1. (optional) Update Gateway API CRDs
If you’re using the Gateway API CRDs, you might want to update them while updating the operator. For the most up-to-date information about installing/updating these, it is best to refer directly to the Gateway API website. https://gateway-api.sigs.k8s.io/2. Update your helm repo
Fetch all the latest updates for your helm repositories to pull down all of the latest ngrok Kubernetes operator chart versions.3. (optional) Find a Specific Release
The following command will print out a list of all the available versions of the ngrok Kubernetes operator chart including development releases. If you want to update to a specific release of the operator instead of updating to the latest version, you can set the following variable to the version of the helm chart (not theAPP VERSION
) you would like to install.
This step is necessary if you plan on upgrading to a development version as helm will never install these versions for you unless you explicitly
specify that you want to install a development version. Development versions are considered any version that does not follow the format <major version>.<minor version>.<patch version>
such as 0.18.0-rc.1
.
Many of the development versions of the ngrok Kubernetes operator follow that format with rc
standing for Release Candidate. These are early development builds before an official release
and may contain features that have not been fully implemented or bugs that have not been identified through testing.
4. Update the Operator with Helm
Set the following variables to the name and namespace of your operator installation. You can check this withhelm list -A
if you did not use the following defaults.
The —reuse-values flag will tell Helm to reuse any values you used in your last install/upgrade. You can change them or add new values by chaining —set flags just like when installing the operator.