Skip to content

Do not require ingress-controller for Gardener setup. - #325

Draft
Gerrit91 wants to merge 4 commits into
masterfrom
remove-gardener-ingress
Draft

Do not require ingress-controller for Gardener setup.#325
Gerrit91 wants to merge 4 commits into
masterfrom
remove-gardener-ingress

Conversation

@Gerrit91

@Gerrit91 Gerrit91 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Description

Follow-up of #299.

  • The kind-cloud-controller-manager did not fully work as it was not possible to run readiness probes against the spawned envoy proxy containers and therefore it did not patch the service status. Running it in the host network resolved this problem.
  • A mutating webhook was added to allow static IPs for the services' type load balancer created by Gardener, dynamically retrieving the correct IPs with .nip.io is really hard to do.
  • All mini-lab status patching workarounds are now gone.
  • Now we also see issues with Netpols for minio as we did for other extensions in the past, too. Here is the PR to deploy them automatically: Allow accessing S3 service inside the Garden Cluster. gardener-extension-backup-s3#31

Used AI-Tools ✨

  • None used for generation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant