The Sequel (patched)

This fixes a role binding issue with the eventing resources, and a certificate chain issue with the HTTP01 solver.

The Sequel (better than the original)

This is still an experimental project, so please use it accordingly.

This release of mink iterates on the initial release, to provide more functionality in an even smaller form factor.

New features this release:

1. The knative.dev/eventing event sources are now bundled (SinkBinding, APIServerSource, PingSource),
2. Tekton Pipelines are now bundled,
3. A new HTTP01 ACME Solver is bundled to provide auto-TLS by default!

Due to the inclusion of Tekton this release the system components have moved to mink-system.

This release also runs the Contour controllers alongside the knative controllers in the same controller pod, for a slightly smaller footprint than 0.12:

kubectl get pod -nmink-system
NAME                          READY   STATUS    RESTARTS   AGE
activator-4mr55               3/3     Running   0          14m
activator-bjqrl               3/3     Running   0          14m
activator-rqf5r               3/3     Running   0          14m
autoscaler-6c6b7c6677-4qch7   1/1     Running   0          14m
controller-76fcd7fdc4-kh9zh   3/3     Running   0          14m

To install this release of mink simply run:

kubectl apply -f release-0.13.0.yaml

This will run a default-domain Job to configure an xip.io domain, however, for auto-TLS to light up, after this Job completes run:

kubectl edit configmap -nmink-system config-domain

The ConfigMap will have an entry that looks like 1.2.3.4.xip.io: "". Copy the IP (1.2.3.4) into a wildcard A record with your favorite domain registrar, and replace this entry with your-domain.dev: "".

... and voila! With this release of mink you can go from a fresh Kubernetes cluster to having TLS-terminated "serverless" services in under 2 minutes. You can even build and deploy these services on-cluster for a FaaS-like experience using the included Tekton integration.

Try it out and send feedback via slack

Initial Release

This is still an experimental project, so please use it accordingly.

This is an initial release of "mink", which runs a curated subset of Knative in knative-system, with a smaller footprint than a standard knative install. The goal of mink is to be a small self-contained Knative install, which is ready to use "out of the box".

mink bundles the new Contour integration (no Istio!) and a Contour installation configured to support Knative that runs alongside the Serving activator component in a DaemonSet (see below).

Here is mink on a three node cluster (note the three activator pods):

NAMESPACE        NAME                             READY   STATUS    RESTARTS   AGE
knative-system   pod/activator-5sxmk              3/3     Running   0          28m
knative-system   pod/activator-bs2mq              3/3     Running   0          28m
knative-system   pod/activator-wmvg7              3/3     Running   0          28m
knative-system   pod/autoscaler-5997d4df9c-nx5pd  1/1     Running   0          28m
knative-system   pod/contour-78c565b99f-j7jpt     2/2     Running   0          28m
knative-system   pod/controller-6cb94799bf-wwbtm  1/1     Running   0          28m

To install this release of mink simply run:

kubectl apply -f release-0.12.0.yaml

Once the default-domain job has completed, you will have a xip.io domain configured and ready to use:

$ kn service create autoscale-go --image=gcr.io/knative-samples/autoscale-go:0.1
Creating service 'autoscale-go' in namespace 'default':

  0.185s The Route is still working to reflect the latest desired specification.
  0.229s Configuration "autoscale-go" is waiting for a Revision to become ready.
  5.999s ...
  6.041s Ingress has not yet been reconciled.
  6.204s Ready to serve.

Service 'autoscale-go' created with latest revision 'autoscale-go-jzlcj-1' and URL:
http://autoscale-go.default.35.224.165.9.xip.io

Try it out and send feedback via slack