-
Notifications
You must be signed in to change notification settings - Fork 40
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
Add InstanceHA Operator #237
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
secret containing the OpenStack admin user password
which one is the secret which has the admin password? iiuc currently only secrets using openstack client configs are used?
By default it uses the same secret used by the openstackclient ( // +kubebuilder:default=openstack-config-secret) . Same for kubebuilder:default=openstack-config. |
/retest |
/test infra-operator-build-deploy-kuttl |
58ef832
to
bf8ca1c
Compare
73034b4
to
f0a2f0c
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
b9b7b3c
to
c6b9533
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm lets get it in and do further enhancements in follow ups
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lmiccini, stuggi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
This commit adds an operator responsible for managing a deployment/pod in charge of evacuating faulty compute nodes. This operator reacts to changes of: configmap containing the InstanceHA configuration file configmap containing the OpenStack clouds.yaml secret containing the OpenStack admin user password secret containing the certificate authority bundle certificate This operator allows running multiple copies (enforcing replica=1) of the InstanceHA service, each with its own configuration file and spec variables, potentially allowing it to be deployed in a multi-cloud/multi-region environment. The InstanceHA service can be deployed by: creating a secret (for example fencing-secret-0) containing something like the following (replacing the value of the uuid key): --- apiVersion: v1 kind: Secret metadata: name: fencing-secret-0 stringData: fencing.yaml: | FencingConfig: compute-0: agent: redfish ipaddr: 192.168.111.9 ipport: 8000 login: admin passwd: password uuid: REPLACEME-0 compute-1: agent: ipmi ipaddr: 192.168.111.10 ipport: 8001 login: admin passwd: password applying a yaml like the provided example under config/samples: apiVersion: instanceha.openstack.org/v1beta1 kind: InstanceHA metadata: name: instanceha-0 spec: caBundleSecretName: combined-ca-bundle fencingSecret: fencing-secret-0 #networkAttachments: ['internalapi'] #openStackCloud: "default" #openStackConfigMap: "openstack-config" #openStackConfigSecret: "openstack-config-secret" #instanceHAConfigMap: "instanceha-config-0" #instanceHAKdumpPort: "7410" spec parameters commented out are optional. The operator will create: configmap "instanceha-0-sh" containing a copy of the python script (templates/instanceha/bin/instanceha.py) configmap "instanceha-0-config" containing a copy of the configuration file (templates/instanceha/config/config.yaml) deployment "instanceha-0" replicaset "instanceha-0-XXX" pod "instanceha-0-XXX-YYY" Related: https://issues.redhat.com/browse/OSPRH-3351
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/8c19325e6fb3465c885da7980707dac1 ✔️ openstack-k8s-operators-content-provider SUCCESS in 10h 34m 46s |
recheck |
@lmiccini: The following test 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-sigs/prow repository. I understand the commands that are listed here. |
This commit adds an operator responsible for managing a deployment/pod in charge of evacuating faulty compute nodes.
This operator reacts to changes of:
This operator allows running multiple copies (enforcing replica=1) of the InstanceHA service, each with its own configuration file and spec variables, potentially allowing it to be deployed in a multi-cloud/multi-region environment.
The InstanceHA service can be deployed by:
spec parameters commented out are optional.
The operator will create: