Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Namespaced deployment overlay generation #301

Merged
merged 3 commits into from
Nov 8, 2024
Merged

Conversation

mikenairn
Copy link
Member

@mikenairn mikenairn commented Nov 7, 2024

fix: Namespaced deployment overlay generation

  • Remove dnshealthcheckprobes CRD for namespaced deployments
  • Add crd to cluster kustomization
  • Improve dns provider generation, avoid calling a base that requires a local file.

bump kustomize version v5.5.0

fix: Multi record test

Test was incorrectly checking for "GEO-" in the aws provider specific endpoint values.

Note: This test is executed on the e2e but only with 1 cluster/deployment so it never uses the second geo, you can re-create the issue by running:

make local-setup DEPLOY=true DEPLOYMENT_SCOPE=namespace DEPLOYMENT_COUNT=2 CLUSTER_COUNT=2
make test-e2e-multi TEST_DNS_ZONE_DOMAIN_NAME=mn.hcpapps.net TEST_DNS_PROVIDER_SECRET_NAME=dns-provider-credentials-aws TEST_DNS_NAMESPACES=dns-operator DEPLOYMENT_COUNT=2 CLUSTER_COUNT=2

We should probably consider adding a GitHub action that executes it this way.

* Remove dnshealthcheckprobes CRD for namespaced deployments
* Add crd to cluster kustomization
* Improve dns provider generation, avoid calling a base that requires a
  local file.

Signed-off-by: Michael Nairn <[email protected]>
Signed-off-by: Michael Nairn <[email protected]>
Test was incorrectly checking for "GEO-" in the aws provider specific
endpoint values.

Signed-off-by: Michael Nairn <[email protected]>
@maleck13
Copy link
Collaborator

maleck13 commented Nov 8, 2024

github action sounds good

@@ -8,3 +8,9 @@ patches:
kind: CustomResourceDefinition
metadata:
name: dnsrecords.kuadrant.io
- patch: |-
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not getting why this is needed?

Copy link
Member Author

@mikenairn mikenairn Nov 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ../../deploy/local kustomization which this is modifying adds the crds which prevents you from using it multiple times in an overlay. When we install multiple instances of the dns operator we can use this kustomization which removes the CRDs multiple times for each namespace we want to install into, and install the crds separately once.

Copy link
Collaborator

@maleck13 maleck13 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm just not sure why we have to remove the probe crd?

@mikenairn mikenairn added this pull request to the merge queue Nov 8, 2024
Merged via the queue into main with commit 8872198 Nov 8, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants