Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Knative and related component versions to latest v0.2x version #509

Closed
Tracked by #680
lamw opened this issue Jul 26, 2021 · 4 comments · Fixed by #683
Closed
Tracked by #680

Update Knative and related component versions to latest v0.2x version #509

lamw opened this issue Jul 26, 2021 · 4 comments · Fixed by #683
Assignees
Labels
enhancement New feature or request

Comments

@lamw
Copy link
Contributor

lamw commented Jul 26, 2021

Is your feature request related to a problem? Please describe.
As part of keeping VEBA BOM up to date, we should update Knative and the respective components such as Knative Contour, RabbitMQ Operator, etc. to latest v0.2x

@lamw lamw added the enhancement New feature or request label Jul 26, 2021
@lamw lamw added this to the v0.7 Release milestone Jul 26, 2021
@lamw lamw self-assigned this Jul 26, 2021
@lamw lamw modified the milestones: v0.7 Release, v0.8 Release Jul 31, 2021
lamw pushed a commit to lamw/vcenter-event-broker-appliance that referenced this issue Jul 31, 2021
Closes: vmware-samples#509
Signed-off-by: William Lam <wlam@vmware.com>
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the stale No activity within the last 60 days label Oct 30, 2021
@lamw
Copy link
Contributor Author

lamw commented Oct 30, 2021

/remove-lifecycle stale

@github-actions
Copy link

Closing issue due to inactivity. Please reopen if needed

@embano1 embano1 reopened this Dec 1, 2021
@embano1
Copy link
Collaborator

embano1 commented Dec 1, 2021

@lamw heads-up when deploying newer RabbitMQ version: you need to set this annotation in the RabbitMQCluster configuration to allow for a Rabbit cluster to be deployed in a different namespace (vmware-system) than the Knative broker (vmware-functions):

metadata:
  annotations:
    rabbitmq.com/topology-allowed-namespaces: '*'

@github-actions github-actions bot removed the stale No activity within the last 60 days label Dec 2, 2021
lamw pushed a commit to lamw/vcenter-event-broker-appliance that referenced this issue Jan 16, 2022
Closes: vmware-samples#509
Signed-off-by: William Lam <wlam@vmware.com>
lamw pushed a commit to lamw/vcenter-event-broker-appliance that referenced this issue Jan 24, 2022
Closes: vmware-samples#509
Signed-off-by: William Lam <wlam@vmware.com>
@lamw lamw closed this as completed in #683 Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants