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

[RFE] Verify if container registry is up & running prior running a workload with builds #389

Closed
rsevilla87 opened this issue Jul 25, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@rsevilla87
Copy link
Member

Is your feature request related to a problem? Please describe.

It would be a nice feature to provide kube-burner the ability to verify if the internal container registry is up and running in the cluster under test.

Describe the solution you'd like

This feature should only affect the OCP wrapper, since it's mainly OpenShift related, just a simple check to query the image-registry cluster operator object to determine if it's ready or not should be enough, I wouldn't verify if it's working well or not for the sake of complexity.

$ oc get co image-registry -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: "2021-01-14T01:23:28Z"
  generation: 1
  name: image-registry
  resourceVersion: "426078413"
  uid: 01fb7ec0-6a44-4c68-bda0-68b606c476ac
spec: {}
status:
  conditions:
  - lastTransitionTime: "2021-01-14T02:07:15Z"
    message: |-
      Available: The registry is ready
      NodeCADaemonAvailable: The daemon set node-ca has available replicas
      ImagePrunerAvailable: Pruner CronJob has been created
    reason: Ready
    status: "True"
    type: Available
  - lastTransitionTime: "2023-07-12T10:19:19Z"
    message: |-
      Progressing: The registry is ready
      NodeCADaemonProgressing: The daemon set node-ca is deployed
    reason: Ready
    status: "False"
    type: Progressing
  - lastTransitionTime: "2023-06-15T11:53:08Z"
    reason: AsExpected
    status: "False"
    type: Degraded

Additional context
In some platforms, like bare metal for example, the internal registry is not configured by default, and running a cluster-density workload would fail without it. Having the ability of reporting if the container registry is up & running prior running the workload would provide a useful information to the user.

@sferlin
Copy link

sferlin commented Aug 11, 2023

@akrzos : When this RFE is part of a new kube-burner release 1, we should update the version installed by jetlag (currently v1.3). I will monitor this in any case, this is just fyi.

@vishnuchalla
Copy link
Collaborator

Closing it as the PR related to this specific RFE is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants