This page describes any specific manual work arounds you may require above and beyond changes described in the News section or using jx upgrade to upgrade the CLI or platform
6th Feb 2019: Regression in jx-install-config secret.
We have spotted a regression in the install process that generates an invalid config file inside the secret jx-install-config secret. Whilst the original defect has been fixed, the invalid secret will create an issue with jx upgrade platform causing the cluster to loose all secrets.
To work around this, we have added some logic into jx upgrade platform to detect the invalid secret and attempt to fix. This feature is included in jx version 1.3.842. An extract of a running upgrade is shown below:
Creating /Users/garethjevans/.jx/adminSecrets.yaml from jx-install-config
Creating /Users/garethjevans/.jx/extraValues.yaml from jx-install-config
We have detected that the /Users/garethjevans/.jx/adminSecrets.yaml file has an invalid format
? Would you like to repair the file? Yes
1st Feb 2019: Changes to the default Nexus configuration
Anonymous access to Nexus has been disabled by default, this has implications to those running Maven based builds. To support this, the maven settings.xml injected into each build pod needs to be modified.
This can be done automatically using:
jx upgrade platform --update-secrets
NOTE: this will regenerate the settings.xml from a defined template.
If you would prefer to apply this changes manually, edit the secret jenkins-maven-settings, duplicating the server block for local-nexus, changing the server id to nexus e.g.
The fixes involve upgrading to a newer version of Prow and Knative Build, the latter caused an issue when performing a traditional jx upgrade addon so we recommend uninstalling Knative Build first (removes Knative Build related Custom Resource Definitions) and install the latest release.
jx delete addon knative-build
And to be extra sure it’s gone maybe do an extra:
helm del --purge knative-build
jx upgrade cli
jx upgrade addon prow
But this means any existing builds or custom changes to BuildTemplate resources will be lost.
5 Jan 2019: environment git repository issue
There was a regression added a few weeks ago which led to new installations setting up invalid exposecontroller configuration in your Staging/Production git repositories. See the issue and workaround
Make sure that the env/values.yaml file for your environment git repository uses expose: as the key in the YAML and not exposecontroller: - if it uses exposecontroller: just edit it back to expose: and you should be good to go!
Also we have noticed a possible regression with helm where if you have multiple expose: sections in your environment env/values.yaml it can disable the exposecontroller post install helm hook which can break the creation of Ingress resources in your environment - if you have more than one expose: sections please combine them into a single entry