Skip to content

Commit

Permalink
Actions kaniko fix (#21)
Browse files Browse the repository at this point in the history
* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* test

* updated refs to new gitlab registry
  • Loading branch information
scottd018 authored Apr 13, 2021
1 parent 7c119a4 commit fc533cf
Show file tree
Hide file tree
Showing 5 changed files with 170 additions and 14 deletions.
1 change: 1 addition & 0 deletions .github/workflows/lint.yml
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ jobs:

check-license-lines:
runs-on: ubuntu-latest
name: Check License Files
steps:
- uses: actions/checkout@master
- name: Check License Lines
Expand Down
38 changes: 27 additions & 11 deletions .github/workflows/publish.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,20 +5,36 @@ on:
tags:
- "v*"
jobs:
publish-to-harbor:
publish-to-registry:
name: Publish to Registry
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Publish to Harbor
uses: aevea/action-kaniko@v0.6.1
- name: Checkout the Code
uses: actions/checkout@v2

- name: Setup Docker Buildx
uses: docker/setup-buildx-action@v1

- name: Generate Tag List
id: meta
uses: crazy-max/ghaction-docker-meta@v2
with:
images: |
${{ secrets.DOCKER_REGISTRY }}/vmware-tanzu-labs/namespace-operator/namespace-operator
tags: |
type=ref,event=tag
- name: Login to Registry
uses: docker/login-action@v1
with:
# Docker registry where the image will be pushed
registry: ${{ secrets.DOCKER_REGISTRY }}
# Username used for authentication to the Docker registry
username: ${{ secrets.DOCKER_USERNAME }}
# Password used for authentication to the Docker registry
password: ${{ secrets.DOCKER_PASSWORD }}
# Image name
image: ${{ secrets.DOCKER_REGISTRY}}/namespace_operator/namespace-operator
# Tags the built image with additional latest tag
tag_with_latest: true

- name: Publish to Registry
uses: docker/build-push-action@v2
with:
push: true
context: .
tags: |
${{ steps.meta.outputs.tags }}
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,9 @@

The namespace-operator project is a project designed for implementing best practices for each namespace created
within a Kubernetes environment. More specifically, it was implemented to take into account best practices
from several years of production-level, field experience from the engineers currently working at VMware. The model
is designed to implement a level of tenancy within each Kubernetes cluster which satisfies many production
from several years of production-level, field experience from the engineers currently working at VMware. While it is
noted that there are several challenges with multi-tenant clusters, for those who desire multi-tenancy within cluster can
use the namespace-operator model to implement a level of tenancy within each Kubernetes cluster which satisfies many production
requirements. Best practices for namespace-operator are derived from guides in the Tanzu Developer Center
(Workload Tenancy Guide) as documented at https://tanzu.vmware.com/developer/guides/kubernetes/workload-tenancy/.

Expand Down
2 changes: 1 addition & 1 deletion config/samples/deployment.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ spec:
serviceAccountName: namespace-operator-admin
containers:
- name: namespace-operator
image: projects.registry.vmware.com/cnr_project_ivy/namespace-operator:v1.2.7
image: registry.gitlab.com/vmware-tanzu-labs/namespace-operator/namespace-operator:latest
imagePullPolicy: Always
resources:
requests:
Expand Down
Loading

0 comments on commit fc533cf

Please sign in to comment.