2023-10-30 10:13:25 -04:00
|
|
|
:_mod-docs-content-type: ASSEMBLY
|
2020-06-23 11:17:33 -04:00
|
|
|
[id="security-deploy"]
|
|
|
|
|
= Deploying containers
|
2022-02-16 11:35:56 -05:00
|
|
|
include::_attributes/common-attributes.adoc[]
|
2020-06-23 11:17:33 -04:00
|
|
|
:context: security-deploy
|
|
|
|
|
|
|
|
|
|
toc::[]
|
|
|
|
|
|
|
|
|
|
You can use a variety of techniques to make sure that the containers you
|
|
|
|
|
deploy hold the latest production-quality content and that they have not
|
|
|
|
|
been tampered with. These techniques include setting up build triggers to
|
|
|
|
|
incorporate the latest code and using signatures to ensure that the container
|
|
|
|
|
comes from a trusted source and has not been modified.
|
|
|
|
|
|
|
|
|
|
// Controlling container deployments with triggers
|
|
|
|
|
include::modules/security-deploy-trigger.adoc[leveloffset=+1]
|
|
|
|
|
|
|
|
|
|
// Controlling what image sources can be deployed
|
|
|
|
|
include::modules/security-deploy-image-sources.adoc[leveloffset=+1]
|
|
|
|
|
|
|
|
|
|
// Signature transports
|
|
|
|
|
include::modules/security-deploy-signature.adoc[leveloffset=+1]
|
|
|
|
|
|
|
|
|
|
// Secrets and ConfigMaps
|
|
|
|
|
include::modules/security-deploy-secrets.adoc[leveloffset=+1]
|
|
|
|
|
|
|
|
|
|
// Continuous deployment tooling
|
|
|
|
|
include::modules/security-deploy-continuous.adoc[leveloffset=+1]
|
2022-02-17 13:08:23 -05:00
|
|
|
|
|
|
|
|
[role="_additional-resources"]
|
2020-06-23 11:17:33 -04:00
|
|
|
.Additional resources
|
2021-02-10 22:55:11 +05:30
|
|
|
* xref:../../cicd/builds/creating-build-inputs.adoc#builds-input-secrets-configmaps_creating-build-inputs[Input secrets and config maps]
|
