diff options
| -rw-r--r-- | blog/the-cult-of-kubernetes-2019-09-07.markdown | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/blog/the-cult-of-kubernetes-2019-09-07.markdown b/blog/the-cult-of-kubernetes-2019-09-07.markdown index 384f901..06a7b78 100644 --- a/blog/the-cult-of-kubernetes-2019-09-07.markdown +++ b/blog/the-cult-of-kubernetes-2019-09-07.markdown @@ -262,8 +262,6 @@ in the future. All I have to do is create a docker image somehow, identify what port should be exposed, give it a domain name and number of replicas and just send it on its merry way. -<center><blockquote class="twitter-tweet"><p lang="hu" dir="ltr">kubernetes is a cult</p>— Andrew Kelley (@andy_kelley) <a href="https://twitter.com/andy_kelley/status/1169999209438859264?ref_src=twsrc%5Etfw">September 6, 2019</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></center> - ## GitHub Actions This does however mean that deployment is no longer as simple as @@ -317,6 +315,8 @@ I am almost _certain_ that I am doing it wrong here, I don't know how robust thi is and I'm very sure that this can and should be done another way; but this is the only thing I could get working (for some definition of "working"). +<center><blockquote class="twitter-tweet"><p lang="hu" dir="ltr">kubernetes is a cult</p>— Andrew Kelley (@andy_kelley) <a href="https://twitter.com/andy_kelley/status/1169999209438859264?ref_src=twsrc%5Etfw">September 6, 2019</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></center> + --- Now when I git push things to the master branch of my blog repo, it will |