![]() With this update, you can use CSI volumes and projected volumes in your pipelines without changing any configuration fields. With this update, the /* and /* reserved annotations are not passed from the pipeline run to the task runs that it creates.īefore this update, CSI volumes and projected volumes were not enabled by default. You can use all features that are marked as beta in the code without further changes. With this update, the enable-api-fields flag is set to beta by default. With this update, the new set-security-context feature flag is set to true by default, in order to enable task runs and pipeline runs to run in namespaces with restricted pod security admission policies. This metric indicates whether the underlying pods are being throttled by OpenShift Container Platform either because of resource quota policies defined in the namespace or because of resource constraints on the underlying node. With this update, the web console includes a new gauge metric for pipeline runs and task runs. Using Tekton Hub with OpenShift Pipelines.Unprivileged building of container images using Buildah.Authenticating pipelines using git secret.Configuring the security context for pods.Using Tekton Chains for OpenShift Pipelines supply chain security. ![]() Using Pipelines as Code with a Git repository hosting service provider.Installing and configuring Pipelines as Code.Viewing pipeline logs using the OpenShift Logging Operator.Using Tekton Results for OpenShift Pipelines observability.Managing non-versioned and versioned cluster tasks.Specifying remote pipelines and tasks using resolvers.Working with OpenShift Pipelines in the web console.Creating CI/CD solutions for applications using OpenShift Pipelines.Setting compute resource quota for OpenShift Pipelines.Reducing resource consumption of OpenShift Pipelines. ![]() ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |