-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[DNM] AGENT-701: day2 add node spike #7465
Conversation
@andfasano: This pull request references AGENT-701 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/draft |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@andfasano: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Discussion thread moved to openshift/enhancements#1517 |
Note
This PR represents a quick-and-rough PoC for the epic AGENT-682, just intended to evaluate the feasibility of the approach for ABI, to support the upcoming design discussion and to hilight potential impacts on the current code. It's not meant to be merged or to represent an implementation proposal, and it uses a totally arbirtrary API that could completely change in its final shape. In addition, it's currently designed to work with just one node.
How to use it
openshift-install
from the current PR and patch it with the desired release version (see billi-release.sh)a.
kubeconfig
file obtained from the previously installed clusterb. A valid plain
pull-secret
filec.
agent-config.yaml
configured as follow (update the MAC address as required):$ openshift-install agent create nodes-image
workers-agent.x86_64.iso
ISO in theextraworker-0
VM and launch it.oc get csr
) and approve them (there should be two, one after the other)oc adm certificate approve <csr-id>
oc get nodes
)