Add an Ingress using a manifest

There are two ways to add a new ingress: manually by using a form or automatically by using a manifest. This article explains how to add an ingress using a manifest.

Manifests aren't just for Ingresses - you can also deploy namespaces, ConfigMaps, secrets and volumes using a manifest.

From the menu select Ingresses then click Create from manifest.

Select the namespace for your deployment, define a name for your Ingress, and then choose the build method from the options provided.

If you want to use namespaces specified in your manifest to define the namespace(s) you wish to deploy to, you can leave Namespace set to default and toggle on the Use namespace(s) specified from manifest option.

Option 1: Git Repository

Use the provided fields to enter the details of your Git repository containing your Kubernetes manifests.

GitOps updates

Enabling GitOps updates gives Portainer the ability to update your application automatically, either by polling the repository at a defined interval for changes or by using a webhook to trigger an update.

For more detail on how GitOps updates function under the hood, have a look at this knowledge base article.

If your application is configured for GitOps updates and you make changes locally, these changes will be overridden by the application definition in the Git repository. Bear this in mind when making configuration changes.

Skip TLS Verification

Enable the Skip TLS Verification toggle to skip checking the validity of the TLS certificate used by your remote repository. This is useful if your repo uses a self-signed certificate.

When you're ready, click Deploy.

Option 2: Web editor

From Deployment type select either Kubernetes or Compose (depending on the format of the manifest) then write or paste in your Kubernetes manifest.

Portainer uses Kompose to convert a Compose manifest to a Kubernetes-compliant manifest. This functionality is planned for deprecation in an upcoming release.

You can search within the web editor at any time by pressing Ctrl-F (or Cmd-F on Mac).

When you're ready, click Deploy.

Option 3: URL

From Deployment type select either Kubernetes or Compose (depending on the format of the manifest) then enter the URL to your manifest file.

Portainer uses Kompose to convert a Compose manifest to a Kubernetes-compliant manifest. This functionality is planned for deprecation in an upcoming release.

When you're ready, click Deploy.

Option 4: Custom template

From the Template dropdown, select the custom template to use. As an optional step, you can edit the template before deploying the application. If you have no custom templates you will be given a link to the Custom Templates section.

When you're ready, click Deploy.

Last updated