-
Sub-task
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
-
False
-
Unset
-
CRCPLAN-232 - AuthZ | PRBAC v2 Service Provider Migration Initiation (Internal)
-
-
-
A&M Tech Debt Q10, Access & Management Sprint 95, Access & Management Sprint 95, Access & Management Sprint 96, Access & Management Sprint 97, Access & Management Sprint 98, Access & Management Sprint 99
As followup to RHCLOUD-34857, the Relations Sink Connector needs to be deployed to production
Requirements:
1. Platform-MQ connect changes would need to be promoted to prod which will roll out a new connect pod for ALL of those services in prod – probably need to coordinate that?
- The new topic needs to be created by bumping to the latest commit in Platform MQ repo
- The Kafka Connect pod needs to be updated to at least THIS commit to ensure the sink plugin is included
- I believe the prod cluster promotion is handled by THIS target which uses a different deploy file than stage. This manifest looks like it expects the image value versus building it which makes sense, uses the same build as stage. The image tag need to match the expected image tag that has the plugin
- Network policies are already in place to allow connectivity between each namespace
- The secret config for the connector will need to be added for prod (stage example)
While troubleshooting stage, a new secret for the connector to authenticate with MSK was needed, we will need to potentially add the same for prod- once the topic and new connect pod are rolled out, and secret is in place, the saas file needs to be updated to add prod target and set correct relations-api-url value to roll out the sink (kessel-inventory-api.kessel-prod.svc:9000)
- clones
-
RHCLOUD-34857 Sink connector: Deployment strategy for sink connector
- Closed
- mentioned on