Skip to content

yogeek/podtato-head

ย 
ย 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Project pod tato Head

Podtato-head demonstrates cloud-native application delivery scenarios using many different tools and services. It is intended to help application delivery support teams test and decide which mechanism(s) to use.

podtatohead

What is it?

Several communicating services are defined in this project with as little additional logic as possible to enable you to focus on the delivery mechanisms themselves.

These communicating services are defined and containerized as encoded in the podtato-services directory. Each contains a simple HTTP server and Dockerfile. main is the externally-accessible endpoint; it communicates with the other services.

Within the delivery directory this set of services and container images is delivered in many different ways to enable you to compare and contrast them. Each delivery mechanism yields the same end result: an API service which communicates with other API services and returns HTML.

Delivery scenarios

Following is the list of scenarios currently implemented. "Single" deployments mean the action effects the state of the resources only once at the time of invocation. "GitOps" deployments mean the action maintains (reconciles) the desired state periodically.

Other scenarios to be targeted in the future:

  • multiple services in different version
  • stateful workloads
  • external dependencies
  • feel free to create issues for use cases you are interested in

Cluster environment

You can use any K8S cluster to run this project. If you do not have a K8S cluster at your disposal, you can quickly get a local one with kind.

NOTE: If you use a cluster with no access to external LoadBalancer (like a kind cluster), you may have to replace type: LoadBalancer by type: ClusterIP (or type: NodePort) in all files declaring a service definition :

# Update service type in all K8S manifests
find delivery -type f -name "*.yaml" -print0 | xargs -0 sed -i 's/type: LoadBalancer/type: ClusterIP/g'
# Update service type in all Helm values
find delivery -type f -name "*.yaml" -print0 | xargs -0 sed -i 's/serviceType: LoadBalancer/serviceType: ClusterIP/g'

Contributing

See contributing.md.

About

๐Ÿ“จ๐Ÿšš CNCF App Delivery SIG Demo

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Go 42.0%
  • Shell 29.5%
  • Dockerfile 8.3%
  • Makefile 6.2%
  • HTML 5.5%
  • Smarty 3.0%
  • Other 5.5%