simonmittag/ingress-j8a

A k8s ingress controller for j8a

ingress-j8a's Issues

Run all unit tests using CircleCI

determine version of kube cluster

Resources Synchronisation Loop with Kubernetes FilteredSharedInformer

Why

The server needs to listen to and update the j8a config for:

• add/remote ingress routes
• updates to services
• updates to configMaps
• updated to secrets

What

We need to regenerate the J8a config for these changes and diff the newly generated config against the currently deployed version. If there is a change, we need to redeploy J8a with the updated config. This should ideally happen in a staged rollout so we're not down.

How

use k8s.io/klog/v2 to log to the kube cluster

Push image to container registry

Why

We need a container registry to publish the ingress controller

What

TBD

Connect to kube apiserver

Generate a j8a config file by reading ingress.yml

Why?

We need to be able to (re) generate the j8a config from ingress.yml and it's changes.

What?

• Read ingress.yml and pluck whitelisted values
• merge with template that includes sensible defaults for fine grained j8a config
• (optional) allow overriding of optional values with meta tags in ingress.ym. (check if this is legal)

How?

• Generate as json, then convert to yml. Take hints from j8a code.
• needs to read links to TLS certs from ingress.yml, follow links and then import them into j8a.config
• (optional) validate config against external j8a cli

Run unit tests using CircleCI

read kubeconfig from file system or the running kube container