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

Release 0.2.0-alpha10 #74

Merged
merged 18 commits into from
Jan 17, 2024
Merged

Release 0.2.0-alpha10 #74

merged 18 commits into from
Jan 17, 2024

Conversation

mijaros
Copy link
Contributor

@mijaros mijaros commented Jan 13, 2024

No description provided.

mijaros and others added 17 commits January 18, 2023 22:23
Clarify exception message
Set architecture for installer properly based on machine arch
Clarify deprecation message
Some OpenShift cluster topologies (single node openshift, schedulable
master nodes) require creating a cluster with zero worker nodes. We want to be able
to deploy clusters with this configuration to more optimally use our
cloud resource quotas. This change is necessary to allow OSIA to
provision a cluster with zero workers. Prior to this change, if you set the count
to zero with the CLI `--worker-replicas` flag, Jinja would interpret
zero as False and therefore use the default value of 3. This moves the
logic for setting the default value to the base cloud class. I moved the master
node replica count logic to the same place for consistency.
Allow setting worker replica count to 0
@mijaros mijaros changed the title Release 0.2.0-alpha9 Release 0.2.0-alpha10 Jan 13, 2024
@mijaros mijaros merged commit a4c0767 into master Jan 17, 2024
8 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.

5 participants