Link Search Menu Expand Document

NAPPTIVE ingress

The napptive-ingress trait creates an Ingress to make the component publicly available to the Internet. The resulting ingress will automatically be given a valid DNS name and associated TLS certificate so that it can be consumed by all major browsers without modification.

The following snippet shows an example application with an napptive-ingress trait to expose an HTTP route on port 80 of the target component. Notice that an https route will be automatically created as major browsers automatically switch to the secure route.

kind: Application
  name: my-app
    version: "v0.0.1"
    description: "My apply-application application"
    - name: component
      type: webservice
        image: my-app-image:v1.0.0
        - port: 80
          expose: true
      - type: napptive-ingress # Set to napptive-ingress      
          name: nginx-ingress # (Optional) endpoint name 
          port: 80 # (Required) port  where the service is listening for incomming connections.
          path: / # (Required) path to be exposed
          rewritePath: / # (Optional) rewrite rule if one is needed.
          targetServiceName: service # (Optional) name of the service associated with the endpoint

Frequently Asked Questions (FAQ)

My application returns 503

The ingress will automatically redirect requests to the component even if the component has just started. Please wait some time depending on the image being execute so that the component is fully up and running.

I expected an http:// endpoint and got https://

Major browsers implement HTTP Strict Transport Security (STS) which translates in automatic promotion of plain requests to https://. We recomended adapting the client consuming the service to support TLS. Alternatively, check your browser documentation to see whether it is possible to switch off this protection layer.