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

wrong mongodb url #62

Closed
indreek opened this issue Jul 26, 2021 · 5 comments
Closed

wrong mongodb url #62

indreek opened this issue Jul 26, 2021 · 5 comments

Comments

@indreek
Copy link

indreek commented Jul 26, 2021

Summary

Cypress-api and cypress-director gets wrong mongodb url: mongodb://cypress-sorry-cypress-mongodb:27017 actual service name is "cypress-mongodb."

Environment

  • helm chart version: 1.0.3
@tico24
Copy link
Contributor

tico24 commented Jul 28, 2021

Can you provide your values? That's certainly not happening for me on my production system.

There's also already mongodb.mongoConnectionString if you want to change it.

@indreek
Copy link
Author

indreek commented Jul 28, 2021

Hi

I have installed it with argocd. I'm already using mongoConnectionString. Otherwise it didn't work.

source:
  repoURL: 'https://sorry-cypress.github.io/charts'
  targetRevision: 1.0.3
  helm:
    parameters:
      - name: mongodb.architecture
        value: standalone
      - name: mongodb.mongoConnectionString
        value: 'mongodb://cypress-mongodb:27017'
    values: |
      mongo:
        enabled: true
      director:
        environmentVariables:
          executionDriver: "../execution/mongo/driver"
          dashboardUrl: "https://cypress.xx.xx.xxx/"
          screenshotsDriver: "../screenshots/s3.driver"
        ingress:
          hosts:
            - host: "cypress-director.xx.xx.xxx"
              path: "/"
          annotations:
            cert-manager.io/cluster-issuer: letsencrypt-prod
            kubernetes.io/tls-acme: "true"
            kubernetes.io/ingress.class: nginx-admin
            nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
          tls:
            - hosts:
                - cypress-director.xx.xx.xxx
              secretName: cypress-director-tls
      dashboard:
        environmentVariables:
          graphQlSchemaUrl: "https://cypress.xx.xx.xxx/api"
        ingress:
          hosts:
            - host: "cypress.xx.xx.xxx"
              path: "/"
          annotations:
            cert-manager.io/cluster-issuer: letsencrypt-prod
            kubernetes.io/tls-acme: "true"
            kubernetes.io/ingress.class: nginx-admin
            nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
          tls:
            - hosts:
                - cypress.xx.xx.xxx
              secretName: cypress-tls
      api:
        ingress:
          hosts:
            - host: "cypress.xx.xx.xxx"
              path: "/api"
          annotations:
            cert-manager.io/cluster-issuer: letsencrypt-prod
            kubernetes.io/tls-acme: "true"
            kubernetes.io/ingress.class: nginx-admin
            nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
          tls:
            - hosts:
                - cypress.xx.xx.xxx
              secretName: cypress-tls
      s3:
        bucketName: "xxx"
        region: "xxx"
        ingress:
          hosts:
            - host: "cypress-recordings.xx.xx.xxx"
              path: "/"
          annotations:
            cert-manager.io/cluster-issuer: letsencrypt-prod
            kubernetes.io/tls-acme: "true"
            kubernetes.io/ingress.class: nginx-admin
            nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
          tls:
            - hosts:
                - cypress.recordings.xx.xx.xxx
              secretName: cypress-recordings-tls
  chart: sorry-cypress

This is my whole config.

@tico24
Copy link
Contributor

tico24 commented Jul 28, 2021

I am also using argocd. Argocd renames the deployment based on the name you define in the application, so this is somewhat expected. There's also the fullname override which I think can be applied to make the two match without defining the connection string, but either way you have to define a thing in the values, so I'd just stick with what you've got.

@indreek
Copy link
Author

indreek commented Jul 28, 2021

understood. Thanks.

@indreek indreek closed this as completed Jul 28, 2021
@tico24
Copy link
Contributor

tico24 commented Jul 28, 2021

I should say that I'm very open to PRs etc that improve on this. I've just done it the way I know how to do it.

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

No branches or pull requests

2 participants