Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/ambassador] AMBASSADOR_ID not set on ambassador-pro containers #15025

Closed
bloxgate opened this issue Jun 24, 2019 · 2 comments · Fixed by #15538
Closed

[stable/ambassador] AMBASSADOR_ID not set on ambassador-pro containers #15025

bloxgate opened this issue Jun 24, 2019 · 2 comments · Fixed by #15538
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@bloxgate
Copy link

Describe the bug
When using Ambassador Pro and a non-default AMBASSADOR_ID, the environment variable needs to be set on both containers, as stated here. However, AMBASSADOR_ID is only set on the ambassador container.

Version of Helm and Kubernetes:
Helm: v2.13.1
Kubernetes: 1.10.11

Which chart:
stable/ambassador v2.8.2

What happened:
A pod containing ambassador and ambassador-pro containers was created. The AMBASSADOR_ID environment variable was only set on the ambassador container.

What you expected to happen:
The AMBASSADOR_ID variable is set on both the ambassador and ambassador-pro containers.

How to reproduce it (as minimally and precisely as possible):
Install the helm chart with the following values:

daemonSet: true

env:
  AMBASSADOR_ID: "ambassador-staging"

pro:
  enabled: true
  licenseKey:
    value: [license key here]

Anything else we need to know:
image

@Bekt
Copy link

Bekt commented Jun 24, 2019

/cc @kflynn @lydiverny

@stale
Copy link

stale bot commented Jul 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants