Skip to content

Match our staging and prod rabbit values#532

Open
DavidFair wants to merge 1 commit intomainfrom
Fix_replicas_for_dev_rabbit
Open

Match our staging and prod rabbit values#532
DavidFair wants to merge 1 commit intomainfrom
Fix_replicas_for_dev_rabbit

Conversation

@DavidFair
Copy link
Copy Markdown
Collaborator

@DavidFair DavidFair commented Apr 13, 2026

Description:

The container is not starting, I suspect this is because the replica count isn't set properly, but to start any further troubleshooting match these values to a known working copy

Adjust the layout to match our prod and staging values to make a diff easier too


Submitter:

Have you:

  • Labelled this PR, e.g. bug, deployment, enhancement ...etc.
  • A deployment can be reviewed, and merged, by a single reviewer.
  • It can only be used to deploy, change, or remove clusters based on existing patterns for staging.
  • Anything involving prod, or production facing services must use the normal 2 person review.
  • All other PR types require the usual PR process (e.g. 2 person).

Reviewer

Have you:

  • Verified this PR uses the correct label(s) based on the rules above?
  • Checked if this could affect production (e.g. a global value that's changed without an override)?
  • Tested setting this up, if it's not a deployment, to verify it can be redeployed with any documentation if appropriate?

@DavidFair DavidFair added the bug Something isn't working label Apr 13, 2026
@@ -1,15 +1,14 @@

stfc-cloud-rabbit-consumer:
replicaCount: 1
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its already set to 1 - https://github.com/stfc/cloud-helm-charts/blob/main/charts/stfc-cloud-rabbit-consumer/values.yaml

you might need to change this file to reflect: https://github.com/stfc/cloud-helm-charts/blob/main/charts/stfc-cloud-rabbit-consumer/dev-values.yaml - which we seem to have not done

stfc-cloud-rabbit-consumer:
  consumer:
    logLevel: INFO
    image:
      repository: rabbit-consumer
      tag: local
      # This allows us to build the image locally and use it in the chart
      pullPolicy: Never
  
    aquilon:
      defaultPrefix: vm-openstack-Dev-
  
    rabbitmq:
      host: dev-openstack.stfc.ac.uk
  
    openstack:
      authUrl: https://dev-openstack.stfc.ac.uk:5000/v3
      computeUrl: https://dev-openstack.stfc.ac.uk:8774/v2.1
      projectId: c9aee696c4b54f12a645af2c951327dc
  
  kerberosSidecar:
    principle: "HTTP/dev-service1.nubes.rl.ac.uk"

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the chart in staging/rabbit-consumer/chart.yml it's still pulling in as stfc-cloud-rabbit-consumer unless we need to match the name in the child of this chart?

I'll drop the 1 from both staging and prod to unify them on that then

@DavidFair DavidFair force-pushed the Fix_replicas_for_dev_rabbit branch from d364674 to 6c90b78 Compare April 13, 2026 14:36
Unifies the staging values and prod by dropping the replica count of prod (to use the upstream
 default similar to staging), and re-order the files to make diff between them easier to see
@anish-mudaraddi anish-mudaraddi force-pushed the Fix_replicas_for_dev_rabbit branch from 6c90b78 to 704cb8c Compare April 23, 2026 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants