DNSPolicy scale testing #1053
DNSPolicy scale testing #1053
Conversation
Adds a new installation overlay `namespaced-dns-operator` that when applied to a cluster will install multiple instances of the dns operator in different namepsaces. Each instance is configured to only watch for dns resources (DNSRecords etc..) in that single namespace. Templates the kuadrant and dns operator versions in config/install overlays. These should be kept in sync with the branch/tag they are for to allow more easily installing a particular version or latest. These will be automicatically updated as part of the release creation. Signed-off-by: Michael Nairn <[email protected]>
* Add hack/dnspolicy-scale-testing to run multi cluster testing scenarios manually on kind clusters * Add basic dns testing config for aws,azure,gcp and inmem providers Signed-off-by: Michael Nairn <[email protected]>
mikenairn
force-pushed
the
scale-testing-dns
branch
from
f8e2e19 to
1987a25
Compare
| dependencies-manifests: ## Update kuadrant dependencies manifests. | ||
| $(call patch-config,config/dependencies/authorino/kustomization.template.yaml,config/dependencies/authorino/kustomization.yaml) | ||
| $(call patch-config,config/dependencies/limitador/kustomization.template.yaml,config/dependencies/limitador/kustomization.yaml) | ||
| $(call patch-config,config/dependencies/dns/kustomization.template.yaml,config/dependencies/dns/kustomization.yaml) | ||
| $(call patch-config,config/install/namespaced-dns-operator/dns-operator/kustomization.template.yaml,config/install/namespaced-dns-operator/dns-operator/kustomization.yaml) | ||
| $(call patch-config,config/install/standard/kuadrant-version.template.yaml,config/install/standard/kuadrant-version.yaml) |
There was a problem hiding this comment.
@maleck13 I added your existing kuadrant install to this task. When we create a release, this will update the kuadrant version to the correct value based on the "VERSION" variable currently set. In the case of main, that will be "latest", but for a semantic version it will be the expected tag e.g. "v1.0.0-rc6"
| @@ -3,4 +3,4 @@ kind: CatalogSource | |||
| metadata: | |||
| name: kuadrant-operator-catalog | |||
| spec: | |||
| image: quay.io/kuadrant/kuadrant-operator-catalog:v1.0.0-rc6 #change this to the version you want to install | |||
| image: quay.io/kuadrant/kuadrant-operator-catalog:latest #change this to the version you want to install | |||
There was a problem hiding this comment.
This is being changed to "latest" because it's on main, this will now get updated to the correct image tag as part of the release process see https://github.com/Kuadrant/kuadrant-operator/pull/1053/files#r1860933307
Installing different versions should be done by checking out the correct version before applying:
git checkout v1.0.0-rc10
kubectl apply -k config/install/standard
or, ideally using a remote ref:
kubectl apply -k github.com/kuadrant/kuadrant-operator/config/install/standard?ref=v1.0.0-rc10
There was a problem hiding this comment.
I don't think the remote will work as the env files are not present
There was a problem hiding this comment.
I'm probably going to close this PR in favour of using kube burner for building the same scale testing scenarios. That said, this image ref on main should probably be pointing to something other than a fixed tag that never gets updated as part of the release. If you are referring to the example apply command i.e. kubectl apply -k github.com/kuadrant/kuadrant-operator/config/install/standard?ref=v1.0.0-rc10, it was just an example of how it could be used if you started updating this image correctly as part of releases.
|
Closing for now, although some of the changes here might come back in another PR. |
DNSPolicy scale testing
part of #928
Installation
Adds a new installation overlay
namespaced-dns-operatorthat when applied to a cluster will install multiple instances of the dns operator in different namespaces. Each instance is configured to only watch for dns resources (DNSRecords etc..) in that single namespace.Templates the kuadrant and dns operator versions in config/install overlays. These should be kept in sync with the branch/tag they are for to allow more easily installing a particular version or latest. These will be automatically updated as part of the release creation.
Testing
Adds a
hack/dnspolicy-scale-testing/test.shscript to run multi cluster testing scenarios manually on kind clustersAdds basic dns testing config for aws,azure,gcp and inmem providers