Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

doc: caveats and peculiarities of container startup sequencing #73

Closed
4 of 5 tasks
draychev opened this issue Mar 15, 2021 · 3 comments
Closed
4 of 5 tasks

doc: caveats and peculiarities of container startup sequencing #73

draychev opened this issue Mar 15, 2021 · 3 comments
Assignees

Comments

@draychev
Copy link

This GitHub issue is to document the caveats and peculiarities of container startup sequencing

  • what happens if the payload container starts before the Envoy is configured and it needs to check connection to the outside world
  • What tools do we have at our disposal to control the sequence of containers starting?
  • What could be expected in logs and Kubernetes events etc when payload container starts before Envoy is ready?
  • point to the Kubernetes issue, which may resolve this in Kubernetes eventually
  • point to the OSM GitHub Issue, which could tackle this within OSM
@shashankram
Copy link
Member

Same as openservicemesh/osm#2316

@shashankram shashankram self-assigned this Mar 22, 2021
shashankram referenced this issue in shashankram/osm Mar 23, 2021
Documents potential application container startup
issues when pods are injected with the sidecar proxy.

Part of #2883

Signed-off-by: Shashank Ram <shashr2204@gmail.com>
@shashankram shashankram assigned draychev and unassigned shashankram Mar 23, 2021
@shashankram
Copy link
Member

@draychev assigning this to you for review phase.

@bridgetkromhout bridgetkromhout transferred this issue from openservicemesh/osm May 21, 2021
@shashankram
Copy link
Member

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants