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

Installing with Non-Gitops Method is not working #54

Open
nemesisOsorio opened this issue Apr 2, 2024 · 3 comments
Open

Installing with Non-Gitops Method is not working #54

nemesisOsorio opened this issue Apr 2, 2024 · 3 comments

Comments

@nemesisOsorio
Copy link

I followed the instructions in the readme using the Non-Gitops Method.
It is creating the pods for halyard, minio, and redis but not the spinnaker services.
I tried this in kubernetes versions:

  • 1.29.2
  • 1.28.7
  • 1.28.6
@odehDanOps
Copy link

I have been trying to follow through this guide on my cluster https://github.com/OpsMx/spinnaker-helm?tab=readme-ov-file#installing-with-non-gitops-method for installation and it doesn't work as well even on a playground

Kubernetes: v1.30.0
Helm: v3.15.3

Skärmbild 2024-07-12 095546

@amrynsky
Copy link

amrynsky commented Aug 1, 2024

The same experience. helm install .... is failing with time out waiting for the condition.

helm: 3.14.3
k8s: 1.30.0

It looks like oss-spin-spinnaker-halyard-0 is not starting properly and oss-spin-install-using-hal-... reports

 curl: (7) Failed to connect to oss-spin-spinnaker-halyard port 8064 after 4 ms: Connection refused                            ││ + sleep 10

Logs from oss-spin-spinnaker-halyard-0 stopped at

2024-08-01 03:16:04.273  INFO 1 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=888e2bef-0739 ││ -3892-afc8-fbe1e9aa3e5a                                                                                                       
2024-08-01 03:16:04.360  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'secretsManagerSecretEn ││ gine' of type [com.netflix.spinnaker.kork.secrets.engines.SecretsManagerSecretEngine] is not eligible for getting processed b ││ y all BeanPostProcessors (for example: not eligible for auto-proxying) 2
2024-08-01 03:16:04.365  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 's3SecretEngine' of typ ││ e [com.netflix.spinnaker.kork.secrets.engines.S3SecretEngine] is not eligible for getting processed by all BeanPostProcessors ││  (for example: not eligible for auto-proxying)                                                                                
2024-08-01 03:16:04.366  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'gcsSecretEngine' of ty ││ pe [com.netflix.spinnaker.kork.secrets.engines.GcsSecretEngine] is not eligible for getting processed by all BeanPostProcesso ││ rs (for example: not eligible for auto-proxying)                                                                              
2024-08-01 03:16:04.366  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'noopSecretEngine' of t ││ ype [com.netflix.spinnaker.kork.secrets.engines.NoopSecretEngine] is not eligible for getting processed by all BeanPostProces ││ sors (for example: not eligible for auto-proxying)                                                                            
2024-08-01 03:16:04.372  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'secretEngineRegistry'  ││ of type [com.netflix.spinnaker.kork.secrets.SecretEngineRegistry] is not eligible for getting processed by all BeanPostProces ││ sors (for example: not eligible for auto-proxying) 
2024-08-01 03:16:04.373  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'secretManager' of type ││  [com.netflix.spinnaker.kork.secrets.SecretManager] is not eligible for getting processed by all BeanPostProcessors (for exam ││ ple: not eligible for auto-proxying)

@amrynsky
Copy link

amrynsky commented Aug 1, 2024

Was able to install providing different versions for halyard & spinnaker

values.yaml

halyard:
  spinnakerVersion: 1.33.0
  image:
    tag: 1.51.0
helm install oss-spin spinnaker/spinnaker -n spin --timeout 1000s -f values.yaml

kudos to @ranesagar #55

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

3 participants