Support a CRC equivalent installation of SNO#1029
Open
steveb wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
Open
Support a CRC equivalent installation of SNO#1029steveb wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
steveb wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
This change adapts the IPv6 lab Single-node-Openshift script to support being installed in an IPv4-only environment which is as similar as possible to CRC. This allows development to occur against a SNO environment when required without bringing up a whole IPv6 lab. Not counting download time SNO installs in 37 minutes vs 7 for CRC, so we can't simply switch to SNO in all scenarios, but making it easier to develop with is desirable in some circumstances. CRC actually supports microshift OKD variants too. This change also adds a CRC_PRESET variable to allow switching CRC variants but this is left undocumented because microshift is missing components such as OLM which the development workflow requires.
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: steveb The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
hjensas
reviewed
Mar 24, 2025
| get_rhcos_live_iso | ||
| create_install_iso | ||
| create_dnsmasq_config | ||
| if [ "${IP_VERSION}" = "v6" ]; then |
Contributor
There was a problem hiding this comment.
We need to set up something for DNS still?
When I tried this, I get this error:
INFO Waiting up to 20m0s (until 11:46AM CET) for the Kubernetes API at https://api.sno.lab.example.com:6443...
ERROR Attempted to gather ClusterOperator status after wait failure: listing ClusterOperator objects: Get "https://api.sno.lab.example.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp: lookup api.sno.lab.example.com on 127.0.0.53:53: no such host
INFO Use the following commands to gather logs from the cluster
INFO openshift-install gather bootstrap --help
ERROR Bootstrap failed to complete: Get "https://api.sno.lab.example.com:6443/version": dial tcp: lookup api.sno.lab.example.com on 127.0.0.53:53: no such host
ERROR Failed waiting for Kubernetes API. This error usually happens when there is a problem on the bootstrap host that prevents creating a temporary control plane.
I think we just set for the IPv4 case?
address=/apps.sno.lab.example.com/${SNO_HOST_IP}
host-record=api.sno.lab.example.com,${SNO_HOST_IP}
host-record=api-int.sno.lab.example.com,${SNO_HOST_IP}
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.
This change adapts the IPv6 lab Single-node-Openshift script to support being installed in an IPv4-only environment which is as similar as possible to CRC. This allows development to occur against a SNO environment when required without bringing up a whole IPv6 lab.
Not counting download time SNO installs in 37 minutes vs 7 for CRC, so we can't simply switch to SNO in all scenarios, but making it easier to develop with is desirable in some circumstances.
CRC actually supports microshift OKD variants too. This change also adds a CRC_PRESET variable to allow switching CRC variants but this is left undocumented because microshift is missing components such as OLM which the development workflow requires.