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

Define the Kubernetes pod and network security policies in jenkins-x platform #1074

Closed
ccojocar opened this issue Jun 18, 2018 · 10 comments
Closed
Labels
area/boot area/security kind/enhancement lifecycle/rotten priority/important-soon

Comments

@ccojocar
Copy link
Member

@ccojocar ccojocar commented Jun 18, 2018

It would be nice to define the POD and Network security policies for Jenkins X platform in order to increase the isolation between the CI/CD platform and the environments where the applications are running.

This could make some users more confident to use the Jenkins X platform in the same cluster with the production environment.

https://speakerdeck.com/ianlewis/kubernetes-security-best-practices?slide=36
https://github.com/freach/kubernetes-security-best-practice

@rajdavies rajdavies added the kind/enhancement label Jun 20, 2018
@madchap
Copy link

@madchap madchap commented Apr 29, 2019

Cilium would probably be useful here (https://cilium.io) and worth a look rather sooner than later, even if it is not doing anything much at first (log only?). Just to avoid as much as possible costly rework down the road. Thoughts?

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot jenkins-x-bot commented Jul 28, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@ccojocar ccojocar added area/boot area/security priority/important-soon and removed area/install priority/important-longterm labels Jan 8, 2020
@ccojocar
Copy link
Member Author

@ccojocar ccojocar commented Jan 8, 2020

/remove-lifecycle stale

@ccojocar ccojocar changed the title Define the Kubernetes security policies in jenkins-x platform Define the Kubernetes pod and network security policies in jenkins-x platform Jan 8, 2020
@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot jenkins-x-bot commented Apr 7, 2020

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot jenkins-x-bot commented May 7, 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

@ccojocar
Copy link
Member Author

@ccojocar ccojocar commented May 7, 2020

/remove-lifecycle rotten

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot jenkins-x-bot commented Aug 5, 2020

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot jenkins-x-bot commented Sep 4, 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot jenkins-x-bot commented Oct 4, 2020

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot jenkins-x-bot commented Oct 4, 2020

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/boot area/security kind/enhancement lifecycle/rotten priority/important-soon
Projects
None yet
Development

No branches or pull requests

4 participants