bf2fc6cc711aee1a0c2a / kas-fleetshard

The kas-fleetshard-operator is responsible for provisioning and managing instances of kafka on a cluster. The kas-fleetshard-synchronizer synchronizes the state of a fleet shard with the kas-fleet-manager.
Apache License 2.0
7 stars 20 forks source link

MGDSTRM-10232 initial configuration to control the ic scope #840

Closed shawkins closed 1 year ago

shawkins commented 1 year ago

Adds a new stanza to the agent spec to control the scope of the ic NLBs.

Since we have a timed job for reconciliation, we don't need to add a specific event handler for the managedkafkaagent - an assumption we were already making about the profile logic.

shawkins commented 1 year ago

Looks like we're still prone to inconsistent test / mock behavior - changed the test to not need the direct mocking.

sonarcloud[bot] commented 1 year ago

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

91.7% 91.7% Coverage
0.0% 0.0% Duplication

shawkins commented 1 year ago

Consider using network instead of net

That's one vote for an annotation, one vote for network, and one vote for access.

Rather than boolean _private use String visibility with enumeration Public and Private

We want to leave open the possibility that this won't be a single case - there could be separate public and private configurations.

shawkins commented 1 year ago

To round things out here:

To combine the above and most of the suggestions, how about just:

spec:
  access: Private

which we will likely throw away once we need refine things further.

MikeEdgar commented 1 year ago

To combine the above and most of the suggestions, how about just:

spec:
  access: Private

which we will likely throw away once we need refine things further.

I'm fine with this ^

rareddy commented 1 year ago

do we need changes here to reflect the above?

shawkins commented 1 year ago

do we need changes here to reflect the above?

Oh, I thought we said on the issue / standup before break, just to leave the pr as is because it's likely a throw away in any case.

rareddy commented 1 year ago

:)