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.

Sign up for GitHub

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

Jump to bottom

[POC] TLS by default #15313

Closed
skabashnyuk opened this issue Nov 26, 2019 · 5 comments
Closed

[POC] TLS by default #15313

skabashnyuk opened this issue Nov 26, 2019 · 5 comments
Assignees
@mmorhun
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Milestone
7.10

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe.

There are several concerns raised here in comments #14742 and we think
that during implementation we may identify quite a lot of corner cases.

Describe the solution you'd like

The goal of this task is:

  • to start the implementation of the task "TLS by default".
  • Identify as much as possible conner cases.
  • Create appropriate issues to implement this task completely.

Describe alternatives you've considered

n/a

Additional context

#14742
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform labels Nov 26, 2019
@skabashnyuk skabashnyuk added this to the Backlog - Platform milestone Nov 26, 2019
@l0rd l0rd mentioned this issue Nov 26, 2019
Closed
6 tasks
@l0rd l0rd added the severity/P1 Has a major impact to usage or development of the system. label Nov 26, 2019
@l0rd
Copy link
Contributor

l0rd commented Nov 26, 2019

Do we really need to have this second issue? I mean now you have this issue + #1472 in your backlog, both with P1, but it looks like the same issue no? I am trying to understand the benefits because from outside it's hard to understand the differences between the 2 issues whereas one single issue for this topic makes things clear.

@skabashnyuk
Copy link
Contributor Author

@l0rd the idea is to have something that we can deliver in one sprint. PLF team think that we are not able to deliver #14742 but we can try to handle #15313

@l0rd
Copy link
Contributor

l0rd commented Nov 27, 2019

@skabashnyuk got it

@tolusha tolusha mentioned this issue Dec 18, 2019
Closed
12 tasks
@mmorhun mmorhun added the status/in-progress This issue has been taken by an engineer and is under active development. label Dec 18, 2019
@tolusha
Copy link
Contributor

tolusha commented Dec 18, 2019 •
edited
Loading

Testing env is minikube

This was referenced Jan 8, 2020
Closed
Closed
@mmorhun mmorhun mentioned this issue Jan 24, 2020
Closed
@tolusha tolusha mentioned this issue Jan 27, 2020
Closed
35 tasks
@mmorhun mmorhun mentioned this issue Jan 30, 2020
Merged
@tolusha tolusha mentioned this issue Feb 17, 2020
Closed
46 tasks
@tolusha tolusha removed the status/in-progress This issue has been taken by an engineer and is under active development. label Feb 18, 2020
@l0rd l0rd mentioned this issue Feb 18, 2020
Closed
7 tasks
@tolusha tolusha removed this from the Backlog - Deploy milestone Feb 19, 2020
@mmorhun
Copy link
Contributor

mmorhun commented Feb 26, 2020

I believe this PoC is done in che-incubator/chectl#476.
Further work will be done in terms of #16052.

@mmorhun mmorhun closed this as completed Feb 26, 2020
@tolusha tolusha added this to the 7.10.0 milestone Feb 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmorhun mmorhun

Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.10
Development

No branches or pull requests
4 participants
@l0rd @skabashnyuk @tolusha @mmorhun