This example starts with four ordinary Kubernetes YAML files. There is no Helm chart and no render step.
The files describe:
one Namespace;
one ConfigMap with a welcome message;
one Deployment with a digest-pinned image and health probes; and
one Service.
The repository proof uploads these files to ConfigHub with one Unit per Kubernetes object. It then reads the Units back and compares them with these files. A separate README Unit explains the example inside Hub.
This example proves the import boundary. It does not claim that the application was deployed or observed on a cluster.
Use this entry in ConfigHub
Every Catalog entry page carries these five steps in this order. Each step says what the Catalog has run for this entry, and a step with a missing precondition gives no command.
Steps 1 and 2 need no account.
What is fixed, and what you supply
Fixed when this entry was built. These went into the build, so the objects already carry them. To change one, build the entry again from its source.
source is examples/plain-yaml/acme-web
objectSetSha256 is 963bf5420b78fbbfa43be7adbb1ced299edef0b2baf0f36850992a6bf66c1926
Yours to supply or check. The listing records no input for the destination. The Catalog has not ruled one out for your cluster.
The Catalog retains this entry's 4 objects as files in the repository, with no single file or inventory to fetch. Open the retained files.
2. Compare with another version or base Not available yet
The Catalog holds no other version or base of this entry's source in the same format. A second entry for plain-yaml-acme-web in this format would give this step a sibling.
3. Upload it as a variant Run for this entry
The Catalog saved this entry in ConfigHub. The listing names no public artifact for it, so no upload command is given. Read the receipt.
4. Deploy it Not available yet
This step needs an upload command from step 3, and this entry has none. A published artifact for this entry, with a receipt, would make this step available.
5. Promote a change Not available yet
This step needs an upload command from step 3, and this entry has none. A published artifact for this entry, with a receipt, would make this step available.
Technical notes and disclaimers
The Catalog keeps no single retained file for this entry, so it has no plain-objects test.