[
https://issues.apache.org/jira/browse/WHIMSY-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848267#comment-16848267
]
Matt Sicker commented on WHIMSY-268:
------------------------------------
While this ticket is not necessarily a replacement for the Puppet
configurations, it could potentially be used to replace that in the future if
Infra wishes to use K8s-native configuration management instead of vanilla
Puppet.
> Cloud native architectural improvements
> ---------------------------------------
>
> Key: WHIMSY-268
> URL: https://issues.apache.org/jira/browse/WHIMSY-268
> Project: Whimsy
> Issue Type: New Feature
> Components: General
> Reporter: Matt Sicker
> Priority: Major
>
> Coming from a development background in devops and cloud native applications,
> I find it somewhat difficult to go back to working on projects with huge
> amounts of variability between environments (production and development in
> particular) and non-trivial manual steps to perform set up or deployment.
> What I'd like to propose here is a cloud native modernization project that
> would consist of the following:
> * Containerize the various services running as Docker images or similar tech.
> * Create Kubernetes configurations (possibly using Helm if needed) for
> running the suite of apps and services for at least running in minikube for
> local development. In the past, I may have suggested writing a docker-compose
> configuration, but that syntax diverged into Docker Swarm which has been
> overtaken by Kubernetes over time as it is.
> This could be an interesting use case for trying out Jenkins X, too, though
> that would be more relevant to overhauling both development and production
> usage, and I'd assume we would need to coordinate with Infra for running
> Kubernetes in production.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
