Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Changing protocols in MessagingEndpoint creates duplicates #5094

Open
ctron opened this issue Jul 30, 2020 · 0 comments
Open

Changing protocols in MessagingEndpoint creates duplicates #5094

ctron opened this issue Jul 30, 2020 · 0 comments
Assignees
Labels
component/shared-infra Targets the shared infrastructure model kind/bug

Comments

@ctron
Copy link
Contributor

ctron commented Jul 30, 2020

It looks like changing the protocol in a messaging endpoint creates a duplicate:

I originally had "AMQPS", and then switched to "AMQP". See final YAML:

  spec:
    host: 192.168.39.114
    nodePort: {}
    protocols:
    - AMQP
  status:
    conditions: 
    host: 192.168.39.114
    internalPorts:
    - name: iot-systemtests-downstream-AMQPS
      port: 40045
      protocol: AMQPS
    - name: iot-systemtests-downstream-AMQP
      port: 40056
      protocol: AMQP
    phase: Active
    ports:
    - name: amqps
      port: 30225
      protocol: AMQPS
    - name: amqp
      port: 30790
      protocol: AMQP
@ctron ctron added kind/bug component/shared-infra Targets the shared infrastructure model labels Jul 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
component/shared-infra Targets the shared infrastructure model kind/bug
Projects
None yet
Development

No branches or pull requests

2 participants