You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MYSQLCLUSTER-8824 Support multiple OLM install modes
Enhanced NDB Operator to support multiple OLM install modes:
- All Namespaces: Cluster-wide scope, allowing the NDB Operator to
monitor NdbCluster resource changes across all namespaces.
- Own Namespace: Limited scope, restricting the NDB Operator to monitor
NdbCluster resource changes only in its own deployment namespace.
- Single Namespace: Customizable scope, enabling the Ndb Operator to
monitor NdbCluster resource changes in a user-specified namespace.
Previously, the `-cluster-scoped` argument offered limited support for
'All Namespaces' and 'Own Namespace' modes, but lacked integration with
OLM settings and proper documentation. This update introduces the
`-watch-namespace` argument, which activates 'Single Namespace' mode
when set with a specific namespace together with
`-cluster-scoped=false`. Additionally, the implementation now seamlessly
integrates with the OLM installation model by checking for the presence
of the WATCH_NAMESPACE environment variable.
Change-Id: I26617cf6678e4a8dde982f39d5f28eb4bbd81df7
To run the operator in a different namespace, the manifest file has to be updated before applying it to the K8s Server.
50
+
To modify the install mode from the default cluster-wide scope, you can set the `-cluster-scoped` argument to `false` in the manifest file. Additionally, you can specify a custom namespace to monitor for NdbCluster resource changes using the `-watch-namespace` flag. If a namespace is provided, the NDB Operator will exclusively watch for changes within that namespace. Otherwise, it will default to monitoring the namespace where the operator itself is deployed.
Copy file name to clipboardExpand all lines: deploy/charts/ndb-operator/README.md
+10-9
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This chart installs the NdbCluster CRD, deploys the Ndb Operator and the webhook
4
4
5
5
## License
6
6
7
-
Copyright (c) 2021, 2024, Oracle and/or its affiliates.
7
+
Copyright (c) 2021, 2025, Oracle and/or its affiliates.
8
8
9
9
License information can be found in the LICENSE file. This distribution may include materials developed by third parties. For license and attribution notices for these materials, please refer to the LICENSE file.
10
10
@@ -64,16 +64,17 @@ Note that removing the NdbCluster CRD will also stop and delete any MySQL Cluste
64
64
65
65
## Configuration
66
66
67
-
The following table has the configurable options supported by the chart and their defaults.
67
+
The following table lists the configurable options supported by the chart, along with their default values.
|`imagePullSecretName`| NDB Operator image pull secret name ||
74
-
|`clusterScoped`| Scope of the Ndb Operator.<br>If `true`, the operator is cluster-scoped and will watch for changes to any NdbCluster resource across all namespaces.<br>If `false`, the operator is namespace-scoped and will only watch for changes in the namespace it is released into. |`true`|
|`image`| The name of the NDB Operator image, including its tag. |`mysql/ndb-operator:latest`|
72
+
|`imagePullPolicy`| The image pull policy for the NDB Operator. |`IfNotPresent`|
73
+
|`imagePullSecretName`| The name of the secret used to authenticate image pulls for the NDB Operator. | None |
74
+
|`clusterScoped`| Determines the scope of the NDB Operator.<br>When set to `true`, the operator watches for changes to any NdbCluster resource across all namespaces.<br>When set to `false`, the operator only watches for changes within its own namespace. |`true`|
75
+
|`watchNamespace`| Specifies the namespace to monitor for NdbCluster resource changes.<br>This option is only applicable when `clusterScoped` is set to `false`. If not specified, the operator will only watch the namespace where it is deployed. | None |
75
76
76
-
These options can be set using the '–set' argument of the helm CLI.
77
+
These options can be set using the '–set' argument of the Helm CLI.
0 commit comments