mamachanko / tanzu-nginx Goto Github PK

View Code? Open in Web Editor NEW

0.0 2.0 0.0 75 KB

A demo Tanzu Nginx package

License: Apache License 2.0

Makefile 86.41% Shell 13.59%

tanzu kapp-controller nginx demo vmware carvel

tanzu-nginx's Introduction

tanzu-nginx

A demo Tanzu Nginx package

Prerequisites

Make sure you have the following available:

kapp (alternatively kubectl)
tanzu CLI (>=0.8.0) will all core plugins installed
credentials for index.docker.io

Prepare your cluster

Install kapp-controller and secretgen-controller:

kapp deploy \
  --app tanzu-components \
  --file https://github.com/vmware-tanzu/carvel-kapp-controller/releases/latest/download/release.yml \
  --file https://github.com/vmware-tanzu/carvel-secretgen-controller/releases/latest/download/release.yml

Provide registry credentials

In order to avoid index.docker.io's rate-limiting, we need to provide credentials:

tanzu secret registry add dockerhub \
  --server index.docker.io \
  --username <YOUR-DOCKER-HUB-USERNAME> \
  --password <YOUR-DOCKER-HUB-PASSWORD> \
  --export-to-all-namespaces

Install the package repository

tanzu package repository add nginx-repo --url mamachanko/tanzu-nginx-repo:0.0.0

... or more conveniently

make repo-install

Installation

tanzu package install nginx \
  --package-name nginx.mamachanko.com \
  --version <version> \
  --values-file sample-values.yml

Cleanup

Uninstall the package with:

tanzu package installed delete nginx

Uninstall the package repository with:

tanzu package repository delete nginx-repo

Uninstall Tanzu components with:

kapp delete --app tanzu-components --yes

tanzu-nginx's People

Contributors

Watchers

tanzu-nginx's Issues

The automated release is failing 🚨

🚨 The automated release from the `1.1.x` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the 1.1.x branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release `1.2.0` on branch `1.1.x` cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.1.1 <1.2.0 can be published from branch 1.1.x.

The following commit is responsible for the invalid release:

feat: a file (5d3aaa2)

This commit should be moved to a valid branch with git merge or git cherry-pick and removed from branch 1.1.x with git revert or git reset.

A valid branch could be main.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀