GitHub Action creating Kubernetes manifest files with Helm, Kustomize, or Kompose
Перейти к файлу
dependabot[bot] 482f7e1335
Bump the actions group across 1 directory with 2 updates (#114)
Bumps the actions group with 2 updates in the / directory: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) and [@vercel/ncc](https://github.com/vercel/ncc).


Updates `@types/node` from 22.8.7 to 22.9.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `@vercel/ncc` from 0.38.2 to 0.38.3
- [Release notes](https://github.com/vercel/ncc/releases)
- [Commits](https://github.com/vercel/ncc/compare/0.38.2...0.38.3)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: "@vercel/ncc"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-11-18 13:20:25 -05:00
.github Bump the actions group in /.github/workflows with 5 updates (#103) 2024-09-11 15:27:33 -04:00
src audit fix (#95) 2024-03-07 11:06:30 -05:00
testResources Vidya reddy/prettier code (#62) 2022-06-28 14:39:10 -04:00
.gitignore Helm namespace feature (#51) 2022-03-01 11:04:06 -05:00
.prettierignore Vidya reddy/prettier code (#62) 2022-06-28 14:39:10 -04:00
.prettierrc.json Vidya reddy/prettier code (#62) 2022-06-28 14:39:10 -04:00
CHANGELOG.md 3.0.1 Changelog (#105) 2024-09-09 09:41:31 -04:00
CODE_OF_CONDUCT.md Vidya reddy/prettier code (#62) 2022-06-28 14:39:10 -04:00
CONTRIBUTING.md Vidya reddy/prettier code (#62) 2022-06-28 14:39:10 -04:00
LICENSE Initial LICENSE commit 2019-10-22 02:44:46 -07:00
README.md v3 release (#96) 2024-03-07 14:30:08 -05:00
SECURITY.md Vidya reddy/prettier code (#62) 2022-06-28 14:39:10 -04:00
action.yml bump Node and Kompose versions (#93) 2024-03-06 18:40:12 -05:00
jest.config.js Vidya reddy/prettier code (#62) 2022-06-28 14:39:10 -04:00
package-lock.json Bump the actions group across 1 directory with 2 updates (#114) 2024-11-18 13:20:25 -05:00
package.json Bump the actions group across 1 directory with 2 updates (#114) 2024-11-18 13:20:25 -05:00
tsconfig.json Vidya reddy/prettier code (#62) 2022-06-28 14:39:10 -04:00

README.md

Kubernetes bake action

Use this action to bake manifest files to be used for deployments using helm, kustomize or kompose.

Sets output variable 'manifestsBundle' which contains the location of the manifest bundles created by bake action.

Example

Bake using helm

- uses: azure/k8s-bake@v3
   with:
      renderEngine: 'helm'
      helmChart: './aks-helloworld/'
      arguments: |
          --ca-file
          ./ca-file/          
      overrideFiles: './aks-helloworld/values-override.yaml'
      overrides: |
          replicas:2          
      helm-version: 'latest'
      silent: 'false'

Bake using Kompose

- uses: azure/k8s-bake@v3
  with:
     renderEngine: 'kompose'
     dockerComposeFile: './docker-compose.yml'
     kompose-version: 'latest'

Bake using Kubernetes Kustomize

- uses: azure/k8s-bake@v3
  with:
     renderEngine: 'kustomize'
     kustomizationPath: './kustomizeexample/'
     arguments: |
        --ca-file
        ./ca-file/        
     kubectl-version: 'latest'

Refer to the action metadata file for details about all the inputs.

End to end workflow for building container images and deploying to a Kubernetes cluster

on: [push]

jobs:
   build:
      runs-on: ubuntu-latest
      steps:
         - uses: actions/checkout@master

         - uses: Azure/docker-login@v1
           with:
              login-server: contoso.azurecr.io
              username: ${{ secrets.REGISTRY_USERNAME }}
              password: ${{ secrets.REGISTRY_PASSWORD }}

         - run: |
              docker build . -t contoso.azurecr.io/k8sdemo:${{ github.sha }}
              docker push contoso.azurecr.io/k8sdemo:${{ github.sha }}              

         - uses: Azure/k8s-set-context@v3
           with:
              kubeconfig: ${{ secrets.KUBE_CONFIG }}

         - uses: Azure/k8s-create-secret@v4
           with:
              container-registry-url: contoso.azurecr.io
              container-registry-username: ${{ secrets.REGISTRY_USERNAME }}
              container-registry-password: ${{ secrets.REGISTRY_PASSWORD }}
              secret-name: demo-k8s-secret

         - uses: azure/k8s-bake@v3
           with:
              renderEngine: 'helm'
              helmChart: './aks-helloworld/'
              overrideFiles: './aks-helloworld/values-override.yaml'
              overrides: |
                 replicas:2                 
              helm-version: 'latest'
           id: bake

         - uses: Azure/k8s-deploy@v4
           with:
              manifests: ${{ steps.bake.outputs.manifestsBundle }}
              images: |
                 demo.azurecr.io/k8sdemo:${{ github.sha }}                 
              imagepullsecrets: |
                 demo-k8s-secret                 

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Support

k8s-bake is an open source project that is not covered by the Microsoft Azure support policy. Please search open issues here, and if your issue isn't already represented please open a new one. The project maintainers will respond to the best of their abilities.