Thundercloud12 commented on PR #6845:
URL: https://github.com/apache/camel-k/pull/6845#issuecomment-5873633617
@squakez so it has been frustrating on me and i think on you as well i think
i was lax in my work earlier i thought fixxinf this one failing test issue
would solve the pipeline but it was not the case i should have been more
thorough with my methods so to actually confirm i ran tests in the below manner:
1. Installed local tooling: Installed kubectl (v1.31.1) and kind (v0.24.0).
2. Created a live cluster: Spun up a real Kubernetes cluster container
(kind-camel-k) with control plane in Ready
state.
3. **Executed setup.sh** directly against the live cluster:
• Operator deployment rolled out and reached 1/1 Running.
• CRDs established.
• Broker StatefulSet my-broker-ss-0 pulled images, initialized, and
reached 1/1 Running.
• Headless service my-broker-hdls-svc was created with port 61616.
• Broker CR reached Ready: True.
• Address CR my-queue created cleanly.
• Script finished with exit code 0 without any timeout.
4. Inspected live cluster state:
pod/my-broker-ss-0 1/1 Running
service/my-broker-hdls-svc 61616/TCP
activemqartemis.broker.amq.io/my-broker Ready: True
activemqartemisaddress.broker.amq.io/my-queue Created
only aftyer this was verified i have pushed the change if you think the
testing methodology should be changed please let me know because that would
avoid us to go into again this ci failing loop
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
