v0.1.18

What's Changed

• Improve documentation by @plan9better in #26
• feat(status): Show status of a connection when running kubectl get ipsecconnections and log errors as k8s events by @plan9better in #28
• Automate building and pushing docker images. by @plan9better in #29
• Move away from using version numbers in docker tags in favour of hashes

Full Changelog: v0.1.17...v0.1.18

v0.1.17

fix an issue where a child would not be restarted when there are other children with the same name from other connections / IKE's in one charon

v0.1.16

release: publish v0.1.16

v0.1.15

Fix an issue where only the first connection per group would be allowed to create pods. This was due to an old status field which is no longer present

v0.1.14

Add charon groups as logical groupings of connections instead of nodes

This allows us to have multiple charon connections on the same node
provided they are not in the host network namespace. With it we're
adding a way to add annotations to charon pod so you can use ipman in
conjunction with other annotation based controllers such as our own
vlanman and multus.

v0.1.13

Fix: metrics doubling connections when there was a rekey
Fix: unloading connections after CR deletion

v0.1.12

Fix an issue where charon pod would use 100% cpu and affect metrics reliability

v0.1.11

Fix an issue with the metrics where multiple children on the same node with the same name would cause the children counter to return 0.

v0.1.10

All of 'extra' field in CR now gets loaded into charon

v0.1.9

Added monitoring via prometheus. It's opt-in. You can enable it via helm values.
Connections will now try to automatically restart if they are down.