We’ve been working hard at adding improvements to the Napptive playground features, and we have added a bunch of cool new features that people are loving. Take a loo below at what’s new in Napptive and remember we would love to hear your feedback if you have something to add!
Adding flexibility in the way applications are deployed on the Playground has been one of our main concerns. While having a static reference application description is key for resiliency and coherency, it is also true that depending on the use case, adding flexibility simplifies a lot of scenarios. For example, if we are debugging an error, we may want to expose extra endpoints, modify its configuration, environment variables, add sidecars, or modify the container image to a custom one. You can now edit the application parameters from the CLI or the Web just before deploying the application without the need to make and modify local copies of it.
For more information, take a look at the revisited getting started tutorial.
One of the most requested features was the ability to use custom domains to access the applications deployed on the Playground. We have added a new property in the Ingress trait which enables you to make use of a custom domain by simply adding a single extra line when launching the application, and adding a CNAME entry on your DNS. We take care of the rest including redirections and TLS certificates.
apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: my-app ... spec: components: - name: my-public-api type: webservice properties: ... traits: - type: napptive-ingress properties: port: 80 path: /extraDNSName: "my.custom.domain"
Catalog is growing
The application catalog provides an immediate way to deploy existing applications into your own environments. The catalog now counts more than 40 applications including Jupyter, Spark, WordPress, and many others. And, private catalog applications are around the corner, so stay tuned!