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

User defined ENV UUID per pod #11417

Closed
kotarusv opened this issue Oct 18, 2016 · 3 comments
Closed

User defined ENV UUID per pod #11417

kotarusv opened this issue Oct 18, 2016 · 3 comments
Assignees
Labels
component/kubernetes lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2

Comments

@kotarusv
Copy link

From: "ccoleman@redhat.com" ccoleman@redhat.com
Date: Tuesday, October 11, 2016 at 12:07 PM
To: Srinivas Naga Kotaru skotaru@cisco.com
Cc: dev dev@lists.openshift.redhat.com
Subject: Re: Container UUID

This should be possible from the downward API as an env var (get the pod uuid as env var) but isn't supported yet.  If you file an issue we can make sure it's exposed, and if important enough we could consider backporting it.

On Oct 11, 2016, at 10:12 AM, Srinivas Naga Kotaru (skotaru) skotaru@cisco.com wrote:
Hi 
 
Is there any way to put an environment variable which hold a unique UUID value per pod basis? If we put an environment variable at dc or rc level, same value propagating for all pods. That is expected behavior since all pods are creating using same template definition
 
If we add environment variable at pod level, its life time is limited.
 
Example:  Want to put an environment variable like below
 
UUID = FCAC382C-0CEB-40E4-9654-07715CDC9DD8
 
This UUID should be unique to each pod.
 
 
-- 
Srinivas Kotaru

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 8, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 11, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/kubernetes lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2
Projects
None yet
Development

No branches or pull requests

5 participants