-
Notifications
You must be signed in to change notification settings - Fork 72
Open
Description
Hi,
-
I have used spinnaker operator to deploy spinnaker on my k8s cluster, after successful deployment all pods are up and running.
-
When I try to add application or project on UI I am met with an error that it can't reach localhost:8084 (gate).
-
I have used NodePort to expose the deck and gate service.
-
So in halyard we use to override the base urls of deck and gate to resolve this issue but in spinaker operator when I try to override base urls it changes the port and nodeport of the services.
-
spinnakerservice.yml looks like:
apiVersion: spinnaker.io/v1alpha2
kind: SpinnakerService
metadata:
name: spinnaker
spec:
spinnakerConfig:
config:
version: 1.25.6
persistentStorage:
persistentStoreType: s3
s3:
bucket: spinnaker
rootFolder: front50
accessKeyId: myaccesskey
secretAccessKey: mysecretkey
pathStyleAccess: true
endpoint: http://10.151.33.41:30679
expose:
type: service
service:
type: NodePort
- So lets say after deployment my deck nodePort is 31000 and gate nodePort is 32000. (deck 80:31000 & gate 80:32000)
- So new spinnakerservice.yml looks like:
apiVersion: spinnaker.io/v1alpha2
kind: SpinnakerService
metadata:
name: spinnaker
spec:
spinnakerConfig:
config:
security:
apiSecurity:
overrideBaseUrl: http://10.151.33.41:32000
uiSecurity:
overrideBaseUrl: http://10.151.33.41:31000
version: 1.25.6
persistentStorage:
persistentStoreType: s3
s3:
bucket: spinnaker
rootFolder: front50
accessKeyId: myaccesskey
secretAccessKey: mysecretkey
pathStyleAccess: true
endpoint: http://10.151.33.41:30679
expose:
type: service
service:
type: NodePort
- But after applying this yaml file, the nodePorts of deck and gate change to new ports and their ports change to 31000 & 32000 respectively. (deck 31000:[new-nodePort] & gate 32000:[new-nodePort])
Any help is appreciated!! Thanks.
Regards,
Nishant
weironz
Metadata
Metadata
Assignees
Labels
No labels