e2e scripts: add rootless podman and local environment support#2362
Closed
delthas wants to merge 9 commits intodevelopment/2.14from
Closed
e2e scripts: add rootless podman and local environment support#2362delthas wants to merge 9 commits intodevelopment/2.14from
delthas wants to merge 9 commits intodevelopment/2.14from
Conversation
… scope When running kind with rootless podman from a graphical terminal, cgroup controllers may not be delegated to the process's cgroup. Detect this and automatically wrap kind create in a systemd scope with Delegate=yes.
Avoid adding duplicate entries to /etc/hosts on re-runs by checking if each zenko.local hostname already exists before appending.
The kind local registry was only partially implemented (missing containerd certs.d configuration on nodes) and was never used by any script. All images are loaded via kind load docker-image. Removing it also fixes a podman networking incompatibility.
When ../zenko-operator exists, symlink it instead of cloning from GitHub. This avoids creating a nested git repo and allows using a local working copy for development. Also clean up the operator image after loading it into kind.
Use $PWD/artifacts instead of /artifacts for kind volume mounts so the setup works outside CI where /artifacts does not exist.
Podman's aardvark-dns (used as the default DNS inside KinD nodes) fails to forward external DNS queries reliably. CoreDNS forwards to /etc/resolv.conf which points to aardvark-dns, causing SERVFAIL for external domains like ghcr.io. When HOST_DNS is set, patch-coredns.sh uses it as the CoreDNS forward target instead of /etc/resolv.conf. The devcontainer setup.sh detects the host nameserver and exports HOST_DNS.
Use a scheme variable based on ENABLE_KEYCLOAK_HTTPS instead of hardcoding https. Use 127.0.0.1 instead of localhost to avoid curl resolving to IPv6 ::1, which kind does not bind on.
Podman injects "dns.podman" into node resolv.conf, which leaks into pod DNS config. CoreDNS cannot resolve this domain, causing 8s timeouts per lookup and killing pods that rely on fast DNS during init (e.g. zookeeper).
Contributor
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Contributor
Missing Jira issueIt is mandatory to specify a Jira issue in the source branch name I could not find such an issue in |
Contributor
Author
|
Oops this was auto-created. Sorry. 😅 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dns.podmansearch domains127.0.0.1instead oflocalhostand add scheme variable for get_token