cerc-io/stack-orchestrator
17
1
Fork 3
Code Issues 113 Pull Requests 18 Actions Packages Projects Releases 480 Wiki Activity

Support optional external container registry #291

New Issue
Open
opened 2023-04-06 14:19:30 +00:00 by dboreham · 2 comments
dboreham commented 2023-04-06 14:19:30 +00:00
Owner
Copy Link

Initial versions of stack orchestrator build all of our containers in situ from source.
We need support the ability to pull pre-built containers from a designated external registry.

Needs: a container tagging scheme that makes sense, a mechanism to change container tags such that they refer to the right registry/version based on user need. Also probably some scheme to "pull if available, built otherwise".

Initial versions of stack orchestrator build all of our containers in situ from source. We need support the ability to pull pre-built containers from a designated external registry. Needs: a container tagging scheme that makes sense, a mechanism to change container tags such that they refer to the right registry/version based on user need. Also probably some scheme to "pull if available, built otherwise".
zramsay commented 2023-04-07 21:56:30 +00:00
Member
Copy Link

And a scheme for e.g., "build all containers, push w/ tag" on release or as necessary

And a scheme for e.g., "build all containers, push w/ tag" on release or as necessary
roysc commented 2023-05-24 13:32:35 +00:00
Member
Copy Link

This would be extremely helpful for CI use

This would be extremely helpful for CI use
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
feature

   
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
in progress

   
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
in progress
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#291
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?