k8s-actions/k8s-create-secret
UshaN 7a93ceb73d Update action.yml with deprecation message (#34)
* Update action.yml

* Update action.yml

* Update action.yml

* Update action.yml

* Update action.yml

* Update action.yml

* Update action.yml
2019-12-04 16:24:40 +05:30
..
lib Refactoring (#12) 2019-07-30 16:02:02 +05:30
src Refactoring (#12) 2019-07-30 16:02:02 +05:30
README.md fixes #27 2019-09-10 20:12:59 +05:30
action.yml Update action.yml with deprecation message (#34) 2019-12-04 16:24:40 +05:30
tsconfig.json Refactoring (#12) 2019-07-30 16:02:02 +05:30

README.md

Kubernetes create secret

Create a generic secret or docker-registry secret in Kubernetes cluster.

The secret will be created in the cluster context which was set earlier in the workflow by using either azure/k8s-actions/aks-set-context or azure/k8s-actions/k8s-set-context

Refer to the action metadata file for details about all the inputs https://github.com/Azure/k8s-actions/blob/master/k8s-create-secret/action.yml

For docker-registry secret (imagepullsecret)

    - name: Set imagePullSecret
      uses: azure/k8s-actions/k8s-create-secret@master
      with:
        namespace: 'myapp'
        container-registry-url: 'containerregistry.contoso.com'
        container-registry-username: ${{ secrets.REGISTRY_USERNAME }}
        container-registry-password: ${{ secrets.REGISTRY_PASSWORD }}
        secret-name: 'contoso-cr'
      id: set-secret

For generic secret

    - uses: azure/k8s-actions/k8s-create-secret@master
      with:
        namespace: 'default'
        secret-type: 'generic'
        arguments:  --from-literal=account-name=${{ secrets.AZURE_STORAGE_ACCOUNT }} --from-literal=access-key=${{ secrets.AZURE_STORAGE_ACCESS_KEY }}
        secret-name: azure-storage

Prerequisite

Get the username and password of your container registry and create secrets for them. For Azure Container registry refer to admin account document for username and password.

Now add the username and password as a secret in the GitHub repository.

In the above example the secret name is REGISTRY_USERNAME and REGISTRY_PASSWORD and it can be used in the workflow by using the following syntax:

container-registry-username: ${{ secrets.REGISTRY_USERNAME }}