This action creates and updates resources in a Kubernetes cluster through running `kubectl apply`. This is the recommended way of managing Kubernetes applications on production.
Push Docker Image Alternatives
Weighing your options? Checkout these 10 alternatives that could help you accomplish your goal.
Helm helps developers manage Kubernetes applications with Helm Charts. The Charts simplify the process of defining, installing, and upgrading K8s apps regardless of their complexity level, serving as a single point of authority. They can be easily versioned, published, and shared with other developers.
This action creates one or more Pods and ensures that a specified number of them successfully terminate using Kubernetes Jobs. A simple case is to create one Job object in order to reliably run one Pod to completion. The Job object will start a new Pod if the first Pod fails or is deleted (for example due to a node hardware failure or a node reboot).
This action executes provided kubectl CMDs against any Kubernetes clusters. In case the commands exit with an error, the action fails.
This action runs a Pod on a Kubernetes cluster. Pods are the smallest deployable units of computing that can be created and managed in Kubernetes. They are most often used in CI/CD workflows for database migrations.
This action updates the image of a container in a selected Kubernetes deployment. In case the commands exit with an error, the action fails.
This action builds Docker image using Dockerfile. It’s also possible to use this action to push a built image to a Docker registry.
This action runs a Docker container using the image built by the action in the previous pipeline or from the provided Docker registry.
This action deploys files from the pipeline’s filesystem to Google Cloud Functions, the Google even-driven serverless compute platform.
This action deploys to AWS Lambda, the Amazon Web Services serverless platform that allows running code without provisioning or managing servers.