github inlets/inlets-operator 0.17.0
Breaking changes to CRD and how tunnels are configured

latest releases: 0.17.9, 0.17.8, 0.17.7...
16 months ago

Generally, we'd expect users to have 1-2 tunnels per deployment, so hopefully this won't affect you too much. Feel free to reach out if you have questions about the upgrade process.

Notes for upgrading:

  • Delete the Operator deployment from the cluster
  • Delete any cloud VMs that were provisioned by the Operator (deleting the Tunnel CR would cause it to be recreated)
  • Delete the old CRD: kubectl delete crd tunnels.inlets.inlets.dev
  • Install the new operator - its CRD is now part of the chart and the license is now created a secret instead of as a flag
  • Update any DNS records you have for the new IP addresses that are created for you

Changelog for 0.17.0:

Commits
e509ddf Remove artifacts due to CRD now being in the chart by @alexellis
e29120c Add CRD to chart instead of applying manually by @alexellis
dad4cad Update CRD printer and set generated in status by @alexellis
340c316 Update when annotations change by @alexellis
54f8da8 New operator namespace and use of secrets by @alexellis
4440082 Bump golang.org/x/text from 0.3.7 to 0.3.8 by @dependabot[bot]
3c094ab Update inlets-pro version used by @alexellis
b7eeea0 Bump github.com/gogo/protobuf from 1.3.1 to 1.3.2 by @dependabot[bot]
82fe992 Bump k8s.io/client-go from 0.18.3 to 0.20.0 by @dependabot[bot]
e82670d Upgrade operator to remove incluster warning by @alexellis

Changes: 0.16.3...0.17.0

Generated by Derek

Don't miss a new inlets-operator release

NewReleases is sending notifications on new releases.