Expose the inventory checker service from the sidecar to outside the cluster (#2)

Merged

rk@tigase.net opened 1 week ago

The inventory checker service in the side car is defined to Uptime Kuma can track it and signal when inventory becomes unavailable due to resource constraints. Hence the service cannot be visible purely within the cluster as it was in the fist PR.

I forgot to expose the service in the first rev of this PR.

Commits were merged into target branch outside of this pull request

Add sidecar container configuration for inventory checker

2 weeks ago

f7965d43

Expose the inventory checker service from sideccar to outside K8s cluster

1 week ago

9cb16637
Ingress policy for inventory-checker-service

1 week ago

715d0ae2
rk@tigase.net commented 1 week ago

I see changes pertaining to James, MySQL, onedev and tigase-xmpp-server. I think that this happened because these changes are in tygrys-testing but not in master.

Since I am targeting my changes into master, these changes are included in the PR. Should I target my PR into tygrys-testing?
Parameterize service port and whitelist addresses in values.yaml

1 week ago

9a770283
Parameterize inventory checker service FQDN using values.yaml

1 week ago

387302d1
Wordsmith inline comments in values.yaml

1 week ago

45df6b59
Andrzej Wójcik (Tigase) commented 1 week ago

I think by default we should be using service as ClusterIP as we want service to not be exposed outside a cluster - we would expose it using ingress, if I'm correct.
Replace unnecessary LoadBalancer with ClusterIP

1 week ago

9ed0b044
OneDev merged pull request 1 week ago
Login to comment

Submitter	rk@tigase.net
Target	master
Source	feature/sidecar-container1

Reviewers

Andrzej Wójcik

Assignees

rk@tigase.net

Merge Strategy

Create Merge Commit

Watchers (3)

Reference

pull request tigase/helm-charts#2