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

[SPIKE] gitea [orgs/apps] -> kube [namespaces/deployments] #329

Closed
jimmykarily opened this issue Apr 26, 2021 · 1 comment · Fixed by #337
Closed

[SPIKE] gitea [orgs/apps] -> kube [namespaces/deployments] #329

jimmykarily opened this issue Apr 26, 2021 · 1 comment · Fixed by #337
Assignees
@jimmykarily

Comments

@jimmykarily
Copy link
Contributor

jimmykarily commented Apr 26, 2021 •
edited
Loading

While we are trying to give less responsibilities to Gitea (See: #308, #328 etc), it makes sense to stop using gitea to list orgs and apps.
We can use kubernetes namespaces to group applications (as in "orgs") and we could list deployments in namespaces to find the applications in an org. This is more kubernetes native approach and also removes that responsibility from Gitea.

Unblocks: #103
@jimmykarily jimmykarily mentioned this issue Apr 26, 2021
Closed
@jimmykarily jimmykarily self-assigned this Apr 26, 2021
jimmykarily pushed a commit that referenced this issue Apr 26, 2021
Use Namespaces as orgs and Deployments as apps
b9f5ad6 
Fixes: #329
jimmykarily pushed a commit that referenced this issue Apr 26, 2021
Use Namespaces as orgs and Deployments as apps
efdfe0f 
Fixes: #329
@jimmykarily
Copy link
Contributor Author

Working branch: https://github.com/epinio/epinio/tree/329-go-native-or-go-home

jimmykarily pushed a commit that referenced this issue Apr 26, 2021
Use Namespaces as orgs and Deployments as apps
cecf209 
Fixes: #329
jimmykarily pushed a commit that referenced this issue Apr 26, 2021
Use Namespaces as orgs and Deployments as apps
9692aef 
Fixes: #329
jimmykarily pushed a commit that referenced this issue Apr 27, 2021
Use Namespaces as orgs and Deployments as apps
f457523 
Fixes: #329
@jimmykarily jimmykarily mentioned this issue Apr 28, 2021
Merged
@manno manno mentioned this issue Apr 29, 2021
Merged
jimmykarily pushed a commit that referenced this issue Apr 29, 2021
Use Namespaces as orgs and Deployments as apps
aea1987 
Fixes: #329

Changes:

- We no longer create an epinio-workloads namespace and the Workloads
  Deployment is gone
- When an org is created we create a namespace and we copy 2 secrets to
  it: The registry credentials that are needed for kube to pull the
  application image (they become ImagePullSecrets of the serviceaccount
  used) and the ca certificate that signs the self-signed certs of the
  applications (used when we don't create production certs).
- When Epinio is uninstalled we delete all the orgs/namespaces.

These changes makes as less dependent on Gitea by removing one
responsibility from it. It is now simply the storage for code. Orgs and
apps concepts now live as Kubernetes primitive objects on the cluster
itself.
jimmykarily pushed a commit that referenced this issue Apr 29, 2021
Use Namespaces as orgs and Deployments as apps
bb21403 
Fixes: #329

Changes:

- We no longer create an epinio-workloads namespace and the Workloads
  Deployment is gone
- When an org is created we create a namespace and we copy 2 secrets to
  it: The registry credentials that are needed for kube to pull the
  application image (they become ImagePullSecrets of the serviceaccount
  used) and the ca certificate that signs the self-signed certs of the
  applications (used when we don't create production certs).
- When Epinio is uninstalled we delete all the orgs/namespaces.

These changes makes as less dependent on Gitea by removing one
responsibility from it. It is now simply the storage for code. Orgs and
apps concepts now live as Kubernetes primitive objects on the cluster
itself.
jimmykarily pushed a commit that referenced this issue Apr 29, 2021
@jimmykarily
Use Namespaces as orgs and Deployments as apps
0fe9afd 
Fixes: #329

Changes:

- We no longer create an epinio-workloads namespace and the Workloads
  Deployment is gone
- When an org is created we create a namespace and we copy 2 secrets to
  it: The registry credentials that are needed for kube to pull the
  application image (they become ImagePullSecrets of the serviceaccount
  used) and the ca certificate that signs the self-signed certs of the
  applications (used when we don't create production certs).
- When Epinio is uninstalled we delete all the orgs/namespaces.

These changes makes as less dependent on Gitea by removing one
responsibility from it. It is now simply the storage for code. Orgs and
apps concepts now live as Kubernetes primitive objects on the cluster
itself.
This was referenced May 11, 2021
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jimmykarily jimmykarily

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

329 go native or go home epinio/epinio
1 participant
@jimmykarily