Skip to content

Upgrade Notes

Release 3.1.0

Breaking changes

Authoritative Server with GeoIP backend and a remote database

The mechanism used by Cloud Control to retrieve GeoIP databases via HTTP and OCI has been improved and now constantly monitors the remote database(s). If a remote GeoIP database is observed to be changed, those changes will be pulled in automatically and the database reloaded.

To enable these new features, the retrieval mechanism was rebuilt and some configuration parameters have been changed. If you were using any of the following prior to Cloud Control 3.1.0 you should have a look at the updated configuration guide at GeoIP Configuration:

  • Remote GeoIP database over HTTP with authentication, TLS and/or using params
  • Remote GeoIP database over OCI with authentication and/or TLS

Deprecation notices

Note: Items listed as deprecated are still available and will continue to function, but they may eventually be removed in a future release.

User management on feeds

Prior to Cloud Control 3.1.0 the recommended method to control user access to feeds (such as Command Source) was via the following parameters:

  • webserverSecretName
  • webserverUsers

These have been deprecated in favor of the following parameters:

  • userSecrets
  • users

In addition, a new default user is now provisioned for each feed, named feeduser.

Reason for this deprecation is the necessity to change the format of the Secret objects in which user credentials are stored. The old mechanism used a username: password format where the username was the key and the password was the value of a key-value pair inside a Secret. The new mechanism uses separate username and password keys, each holding their corresponding values.

These new parameters, along with the deprecated ones, are further described on each feed's corresponding configuration guide.

Miscellaneous

Grafana objects renaming

Due to the upgrade of the Grafana Operator, most Grafana-related objects now have v2 included in their names to allow for an upgrade without collision between the old & new versions. Most notable is the change to the name of the default Service object, which will change from grafana-service to grafana-v2-service.

Note: Configuration options exposed by the monitoring Helm Chart for Grafana remain unchanged.