-
Notifications
You must be signed in to change notification settings - Fork 194
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
103 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
43 changes: 43 additions & 0 deletions
43
...pool/global-spec-config-for-multicluster-with-HA-CIS-and-cluster-admin-state-no-pool.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
# Example for the usage of adminState with no-pool value in the extendedConfigmap in case of HA-CIS. | ||
# adminState can be provided for a cluster to mark the state of a particular cluster. | ||
# Supported values for adminState are [enable, disable, offline] | ||
# By default clusters are in enabled state. | ||
# adminState: enable, all new connections are allowed to the pool members from the cluster. | ||
# adminState: disable, all new connections except those which match an existing persistence session are not allowed for the pool members from the cluster. | ||
# adminState: offline, no new connections are allowed to the pool members from the cluster, even if they match an existing persistence session. | ||
# adminState: in ratio mode, a service pool is not created for the affected cluster. For all other modes, pool members from the cluster are not added to the service pool. This configuration is helpful when we don't want to add pool or pool members from a particular cluster due to any reasons(for example cluster is under maintenance). | ||
|
||
apiVersion: v1 | ||
kind: ConfigMap | ||
metadata: | ||
labels: | ||
f5nr: "true" | ||
name: extended-spec-config | ||
namespace: kube-system | ||
data: | ||
extendedSpec: | | ||
mode: active-active | ||
highAvailabilityCIS: | ||
primaryEndPoint: http://10.145.72.114:8001 | ||
probeInterval: 30 | ||
retryInterval: 3 | ||
primaryCluster: | ||
clusterName: cluster1 | ||
secret: default/kubeconfig1 | ||
secondaryCluster: | ||
clusterName: cluster2 | ||
secret: default/kubeconfig2 | ||
adminState: no-pool | ||
externalClustersConfig: | ||
- clusterName: cluster3 | ||
secret: default/kubeconfig3 | ||
adminState: offline | ||
- clusterName: cluster4 | ||
secret: default/kubeconfig4 | ||
adminState: no-pool | ||
extendedRouteSpec: | ||
- allowOverride: false | ||
namespace: foo | ||
policyCR: foo/cr-policy1 | ||
vserverAddr: 10.8.0.4 | ||
vserverName: vs-foo |
Oops, something went wrong.