Skip to content

Conversation

dmichel1
Copy link

If a custom healthEndpoint is defined it should be used otherwise k8s will never mark the node as ready.

I encountered this bug with the below config. Its using a custom context-path and a legacy server port.

profiles:
  gate:
    servlet:
      context-path: /api/v1

service-settings:
  gate:
    healthEndpoint: /api/v1/health
     server:
       port: 9002
     default:
       apiPort: 8085
       legacyServerPort: 8084

Related to spinnaker/spinnaker#2533

@dmichel1 dmichel1 changed the title Use healthEndpoint if defined when transforming a server port fix(transformer): Use healthEndpoint if defined when transforming a server port Apr 17, 2021
If a custom healthEndpoint is defined it should be used otherwise k8s will never mark the node as ready.

I encountered this bug with the below config.

```yaml

profiles:
  gate:
    servlet:
      context-path: /api/v1

service-settings:
  gate:
    healthEndpoint: /api/v1/health
     server:
       port: 9002
     default:
       apiPort: 8085
       legacyServerPort: 8084

```

Related to spinnaker/spinnaker#2533
@dmichel1 dmichel1 force-pushed the dmichel/custom-health branch from 7da7b80 to f431286 Compare April 17, 2021 20:57
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

Successfully merging this pull request may close these issues.

1 participant