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.

Sign up for GitHub

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

Jump to bottom

Provide clarity on the differences between OCM native app lifecycle addon vs ArgoCD pull integration #314

Closed
mikeshng opened this issue Nov 17, 2023 · 1 comment
Closed

Provide clarity on the differences between OCM native app lifecycle addon vs ArgoCD pull integration #314

mikeshng opened this issue Nov 17, 2023 · 1 comment
Assignees
@mikeshng
Labels
documentation Improvements or additions to documentation Stale

Comments

@mikeshng
Copy link
Member

We should provide clarity on the long term plan for OCM native addon application lifecycle management and Argo CD pull integration.

As users discovered, both projects are similar and they want a better long term strategy and roadmap on these two projects.

More details:

  • Initially we wanted to completely move away from the native addon.
  • However, there are production users using the native addon approach.
  • We want to inform new users to start using the Argo CD integration but also keep the promise of continuing AppSubscription for existing users.
@mikeshng mikeshng added the documentation Improvements or additions to documentation label Nov 17, 2023
@mikeshng mikeshng self-assigned this Nov 17, 2023
mprahl pushed a commit to mprahl/OCM that referenced this issue Mar 14, 2024
@zhiweiyin318
upgrade image builder (open-cluster-management-io#314)
78fc1f5 
Signed-off-by: Zhiwei Yin <zyin@redhat.com>
mprahl pushed a commit to mprahl/OCM that referenced this issue Mar 14, 2024
@ldpliu
update min tls to 1.13 (open-cluster-management-io#314)
f3a5fca 
Signed-off-by: ldpliu <daliu@redhat.com>
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

@github-actions github-actions bot added the Stale label Mar 17, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikeshng mikeshng

Labels
documentation Improvements or additions to documentation Stale
Projects
OCM releases
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mikeshng