v1.5.8-release

Full Changelog: v1.5.7...v1.5.8-release

v1.5.8

Full Changelog: v1.5.7...v1.5.8

v1.5.7-release

What's Changed

• fix(): Fixed security vulnerabilities by @mridulgain in #13
• fix(): Updated nsm sdk to a version custom made for NSCs by @mridulgain in #14

New Contributors

• @mridulgain made their first contribution in #13

Full Changelog: v1.5.6...v1.5.7-release

v1.5.7

What's Changed

• fix(): Fixed security vulnerabilities by @mridulgain in #13
• fix(): Updated nsm sdk to a version custom made for NSCs by @mridulgain in #14

New Contributors

• @mridulgain made their first contribution in #13

Full Changelog: v1.5.6...v1.5.7

v1.5.6-release

Cloud Access Service Gateway
KubeSlice now supports onboarding cloud-managed services onto a slice. The feature is called Cloud Access Service Gateway.

All the application pods on that slice can access the onboarded cloud-managed service.

What's Changed

• fix(): Apply workaround to nsmgr tcp connection by @bharath-avesha in #4
• Fix(): Derive nsmgr service name from node name by @bharath-avesha in #5
• fix(): Kick the build with semantic commit by @bharath-avesha in #6
• fix(): Use nsmgr svc name derived from hash of node name by @bharath-avesha in #7
• fix(): Modify resolv.conf to workaround istio dns issue by @bharath-avesha in #8

Full Changelog: v1.5.3-release...v1.5.6-release

v1.5.6

Cloud Access Service Gateway
KubeSlice now supports onboarding cloud-managed services onto a slice. The feature is called Cloud Access Service Gateway.

All the application pods on that slice can access the onboarded cloud-managed service.

Full Changelog: v1.5.5...v1.5.6

v1.5.5-release

v1.5.5-release

What's Changed

• fix(): Apply workaround to nsmgr tcp connection by @bharath-avesha in #4
• Fix(): Derive nsmgr service name from node name by @bharath-avesha in #5
• fix(): Kick the build with semantic commit by @bharath-avesha in #6
• fix(): Use nsmgr svc name derived from hash of node name by @bharath-avesha in #7
• fix(): Modify resolv.conf to workaround istio dns issue by @bharath-avesha in #8

Full Changelog: v1.5.3-release...v1.5.5-release

v1.5.4-release

What's Changed

• fix(): Apply workaround to nsmgr tcp connection by @bharath-avesha in #4
• Fix(): Derive nsmgr service name from node name by @bharath-avesha in #5
• fix(): Kick the build with semantic commit by @bharath-avesha in #6
• fix(): Use nsmgr svc name derived from hash of node name by @bharath-avesha in #7

Full Changelog: v1.5.3-release...v1.5.4-release

v1.5.3-release

fix(): Setup DNS config in resolv.conf (#2)

Backed up the original resolv.conf and overwrote its contents to
redirect dns queries to the cmd-nsc sidecar.
This was needed because istio-proxy that runs as one of the
sidecars seems to read the resolv.conf during bootup and cache the config.
Any subsequent change to the resolv.conf is not picked up by the proxy. So
if the cmd-nsc sidecar takes time to boot up and modify the resolv.conf for
all the other containers, the istio-proxy sidecar would have read the
original resolv.conf and ignored the config written by cmd-nsc. This causes
name resolution to fail in istio-proxy for the domains that are serviced by
a custom dns server other than the default kube-dns.

Signed-off-by: Bharath Horatti <[email protected]>

Signed-off-by: Bharath Horatti <[email protected]>

v1.5.2-release

cmd-nsc-init for kubeslice oss 0.5.0 release