After our Head Of Software has terminated.

I started to take control over our development crew. And in this year I did more then the old head in the last 6 years.
- Swapped from plain old SVN to Gitlab.
- Build a complete autonomous deployment with Gitlab.
- Introduced code reviews.
- Started to refactor the legacy product with 500.000 lines of code...
- learned how to use confluent apache kafka and kubernetes to split the legacy project in many small and maintainable one.(not done yet)
- Last 3 weeks I learned how to use elasticstack with kibana and co. That we aren't blind anymore. Big dashboards are now shown in the middle of the room :) and maybe convinced my coworker that we use unity3d for our business application cause of support for all devices and same design on them. And offline capabilities. (Don't know if this was my best idea)
When I look back, I'm proud to did that much in one year alone. And my coworkers are happy too that they have less work with deployments and everything.
But I can't decide what's the title for this. System or Software Architect cause I litterallity did both :/

As a full time remote employee it gets lonely. Im getting ready to turn my home into a co-working space :

* Plenty of space with tables and couches

* Gigabit Internet backed by enterprise networking gear

* Lots of fresh ground coffee

* Local Kubernetes server !

* dog friendly chill space

* kid friendly play areas during the summer

* Mountain home with backyard hiking trails , wildlife lookout (wild deer live in my back yard), and fireplaces

What else would you want in your co-work space-at-my-place (TM)?

Finish my Raspberry Pi Zero Cluster... complete with kubernetes, etc.

... I still don't know what I'm going to run on this. suggestions in the comments welcome.

The 2014's called, they want their private server back!

Source: CommitStrip

We've got a team of around 20 developers and the most junior of them all is a interesting specimen.

The kind of person who thinks they a 'expert' in anything and everything and is constantly trying to school our senior developers who have 20+ years experience behind them.

The sort of person that spends 15 seconds googling something he has never heard of before, but now that he has skimmed 1 page on Google would classify himself as a 'expert' in said topic.

He comes into my office yesterday and proclaims that it has been decided by himself that he no longer wants to be a developer anymore and wants to do Ops/Infrastructure, then starts rambling on about how he is a Kubernetes expert.

I asked what experience he had with Kubernetes and his response was "I watched a webinar they did last night" to which I asked if he had ever actually used anything to do with Kubernetes in his life.

"No, but I'll watch a few YouTube videos and will then be more than qualified" he says

Followed by him telling me that we'll be moving all of our current Docker Swarm clusters into Kubernetes.

This was news to me (I'm head of infrastructure and operations)

I needed a good giggle, so I asked why we would get rid of our exisiting Docker infrastructure that's got a 100% uptime over the past 2 years and has worked without failure. It's truely been a dream.

He says "Because it's shiny and cool and better"

The nest afternoon he comes to me and says "When I move everything into Kubernetes I am going to convert everything into micro services"

He says that he watched a YouTube video the night before on microservices and has decided that it's what we need to use for a particular project.

(It's a simple php website that gets 100 hits per day)

Hopefully his boss will notice that he is producing no output soon. Don't want to tell the manager that the guy he hired delivers no work and lives in a fantasy land.

"your not touching the infrastructure. Ever"

I am trying to understand something for a while. devRant is full of privacy advocates and to be honest, part of it is almost taken by a group of people that call other people random swear words people because they are using a particular product of a company.

I will raise some points and will try to discuss them with other people in comments.

I will stick with Google. Since it looks like it's the most hated one. A company that has built one of the most intelligent infrastructure, the most popular mobile operating system and of course, the best search engine currently available.

The problem everyone sees is the privacy. Google tracks the search history to give users a better experience and show relevant ads. You might not need this "better experience". In case you don't know, you can turn off personalized search any time to make sure Google doesn't track. Same goes with Google Chrome, you can turn off all the data it is sending to servers in settings. You can simply not sign in if you don't anything to be synchronised.

An argument is Google should be opt-in rather than opt-out. But the general users are not tech-savvy. And yes, going to settings and turning on personalised search is a lot of work for a huge amount of people. Trust me, I worked in IT before. If they find other search engine giving them a good experience without changing anything in the settings, they will just simply move to that engine.

What interests me most if how people back DuckDuckGo. First of all, not all parts of DDG is not open source (it's fucking not, you can argue all day). Parts of it is closed because of licensing issues.

That is perfectly fine to privacy community. But it's not when Chrome is closed source for almost the same reason. I mean when you're using DDG, you are supporting a US-based company that has privacy all over its face and using closed source application on their server. Have you not learned anything from history?

You might be wondering about my obsession with Google. It hurts me when I see a giant company whose popular software is open source is bashed like this. Google has made huge contributions to open source communities. Chromium, Android, Kubernetes, Angular, GoLang, TensorFlow etc.

And PRISM, how do you know that DDG is not part of it? it's US-based after all.

I just saw an article that used a video with a title "TNW - Aral Balkan - Free Is A Lie | The Next Web" while asking us to switch to DDG. Ummm....DDG is also free right?

Maybe we should raise concerns with the US gov first rather than Google.

My weekend project. Anyone else built a Raspberry Pi 3 cluster (for Kubernetes)?

Rare footage of me waiting for my Kubernetes cluster to start.(2018BC,colorized)

I was sleeping next to my wife and suddenly I raised my hand and shouted "gaaaa", when she asked what is wrong, I replied
"Kubernetes is misbehaving"
without waking up

Is it me or doing forty minutes standup meetings every morning is a complete waste of everyone's time? I don't need to explain what is Kubernetes and how to install it to my boss...

Since fucking when did "bare metal" mean just running on an OS?? At a conference and literally everyone is like "we got kubernetes running on bare metal", got super excited for a bit because just the idea of that sounds amazing but they're using it as slang for "basically not in a container or vm."

Nothing exciting at all. Now we're patting ourselves on the back for getting software working without it being preconfigured as a container or a VM image. No one knows how to do anything any more. MUCH too much abstraction going on.

I guess it keeps me more employable, but the state of the world from a developer standpoint is just sad.

(For reference, this is what the first sentence of "Bare Metal" looks like on wikipedia "In computer science, bare machine (or bare metal) refers to a computer executing instructions directly on logic hardware without an intervening operating system.")

To me, it seems like the rise of distributed systems like mesos / kubernetes combined with Docker require you to be master sysadmin, veteran kernel hacker and a part time c developer ALL AT ONCE if you really want to shave off time from debugging/ performance tuning sessions. Anyone wish they paid more attention in class ? Lol.

Black Friday fail.

Local online store totally failed last year on BF, so they spent the whole week on news, radio, print ads, newsletter raving about how they upgraded the systems for BF and are expecting double the traffic of last year and are super ready. 60 seconds into BF, site went totally tits up, was not till 01:45 that anyone could access it again, and according to uptimerobot, they were tits up for about 55% of the day.

fren: do you have a date this valentines?

me: nah fam

fren: what u doin rn

me: [Insert technical explanation of Kubernetes here]

fren: [goes offline]

I work in a contract position and reviewed the code of a senior engineer recently. Regretfully I can't provide context to preserve anonymity.

He wrote awful JavaScript;

- handled a single DOM element with 2 different frontend libraries
- used the logical operator && to 'chain' two methods (it didn't work) instead of returning a boolean value,
- broke everything down into minute detail (a comment box had 7 components!),
- API calls were made for every component update instead of maintaining local component state where it made sense, which meant UI updates were slow,
- animated EVERYTHING, which made my Firefox on Xubuntu i7 64bit with 16GB RAM beg for mercy.

I had a rough couple of months with interviews, with 2nd stage technical interviewers throwing impossible tasks at me.

Example:

1. Create an online Python code editor with Javascript which can compile Python bytecode,
2. Use Mesos and Kafka to create real time architecture for Tensorflow with a Javascript frontend in 1 day. (I asked, and wasn't allowed to use Kubernetes or serverless architecture),
3. Hack a website from the browser's address bar using parameters ( what?!! ),

Obviously, the next time I meet a 'senior', I'm going to tell him talk is cheap;

'SHOW ME YOUR CODE.'

Just another normal conversation as a Kubernetes Operator

Is the technical term for a failed Kubernetes deployment a "clusterfuck"?

[Applies for RedHat OpenShift Beta on April]

this will be lit I said, since I was quite a bug reporter for Eclipse Che/Codenvy

[Took me until november to open up a ticket so they can take me in]

oooh shit this is lit

[Starts an Eclipse Che Workspace]

huh, why isn't it provisioning?

[inb4 OpenShift devs says its both a OSIO infra issue and a known bug in the OpenShift panel]

oof.

[Makes it work using workaround]

Woo this is gon-

[Haha no, Too Many tedirects for you]

REEEEEEEEEE

Conclusion: Openshift.io is a lit platform, it just happened to be very VERY beta.

I like the kubernetes "pods" tho

Inherited a simple marketplace website that matches job seekers and hospitals in healthcare. Typically, all you need for this sort of thing is a web server, a database with search

But the precious devs decided to go micro-services in a container and db per service fashion. They ended up with over 50 docker containers with 50ish databases. It was a nightmare to scale or maintain!

With 50 database for for a simple web application that clearly needs to share data, integration testing was impossible, data loss became common, very hard to pin down, debugging was a nightmare, and also dangerous to change a service’s schema as dependencies were all tangled up.

The obvious thing was to scale down the infrastructure, so we could scale up properly, in a resource driven manner, rather than following the trend.

We made plans, but the CTO seemed worried about yet another architectural changes, so he invested in more infrastructure services, kubernetes, zipkin, prometheus etc without any idea what problems those infra services would solve.

Kubernetes Note:
"Default" is not the default DNS policy.

OK!!!! (╯°□°）╯︵ ┻━┻

I got 4 raspberry pi's with docker next to me. What's the best way to orchestrate them?
Kubernetes, docker swarm, other?

I finally bit the bullet and got a 2018 macbook pro i7 with 1 terabyte ssd. I've been needing a personal laptop for development for awhile. I thought about going full Linux but it's tough finding Linux laptops that support thunderbolt 3 charging.

I tried to make Windows and WLS work. But it's a pain getting my Golang, GCP, and Kubernetes workflow setup on it. I keep having to jump command prompts and it annoys the shit out of me. Going multi monitor helps a lot, but I like to be at coffee shops and code.

I feel sick a out giving Apple more money especially $3,000. But it was money well spent. My workflow is seamless and unlike on my Windows laptop I dont spend 3 to 4 days just setting up my environment.

Here it goes my second Rpi cluster 😎
Actually there are 3 Orange Pi PC, 1 Rpi3, 1 Rpi2 and an Odroid XU4.
I plan on using it as a workbench for many technologies.
For example DevStack, Ansible, Gluster, TahoeLAFS, Kubernetes, Docker Swarm and such.
Any additional suggestions?

What is kubernetes, what is docker, and what is a container?

Spent ten plus years professionally coding, used c, go , python, openwhisk ,docker, kubernetes and God know what else. Now I have to convince those team members who coded so far in their free time that write fucking clean code, avoid dependency on distributed and hard coded configuration, how to build a product
Fuck my life

Hey guys i wanna build a Pi-like Cluster to try out kunernetes locally and I would like some parts advice for the boards, casing, cooling, and the rack itself.

so far I have a Cisco E1200 Router I would use for the cluster for SSHing and connecting to

I'm currently planning to set myselv up with some vps/dedicated server's for a project. What i plan to do to secure these servers is.
*Use centos 7
* Setup Wireguard and join all of the servers +1 client (my pc) to that network
*Disable SSH Access from outside that VPN
*Only allow RSA Key login to the Servers
*Install Cockpit for monitoring
*Intall docker/kubernetes for the applications i plan to run

What do you guys think of that as a baseline? Im not sure if my lower powered VPS (VPS M SSD from Contabo) will work as Kubernetes Nodes, does anyone have experience with that?

In general these Servers will be used for my projects and other fooling around.

If you guys have other suggestions for Securing/monitoring or other software i could put on to have more control without eating up to much of the Servers power, let me know :D

About two weeks ago, at my workplace, I learnt about Django deployment in Nginx server with Docker and Kubernetes on Google Cloud Console.

one thing I don't get from Kubernetes

if a group of containers are called pods, and pods are containers, and containers in Kubernetes are also inside containers, therefore, its a clusterfuck of containers?

Kubernetes is actually sick. I love learning about it and playing around with localized clusters. The only thing that sucks is I would never use this for anything while I'm still a CS student. And I probably won't ever use this if I'm not in Devops. *sigh*. fun to learn about, regardless.

Don't use your senior software engineer title or years of experience as reasons in a debate or argument about software

My manager was asking me what steps needs to be done to perform a disaster recovery for our cluster( on production). I will be honest here, I have not maintained this type of cluster(kubernetes) in production before. However, I have enough understand of the system to answer my boss question. I basically told him there are A, B, C you have to do.

My senior developer jumped in and said "No you should do A,C, B because C is more critical than B. " I then replied to him: "I understand your point, I notice that too, but .." Before I can even finish my sentence, this dude has already rolled his eyes and interrupted me very loudly: "Have you worked with these systems on production before? I did". The asshole knows I haven't maintained Kubernetes on production yet of course.

I got super pissed at him and pretty much shouted back to him and my manager: "Just because I haven't worked on this system on production yet, does not mean my argument is wrong" .

I then dragged my managers, that asshole, and other engineers in a room and settle this out. In the end, people agreed with my steps over that asshole senior engineer dude because I gave them rational reasons.

The conclusion is: Your senior title is given by the company, It doesn't mean anything to me. Also, it doesn't make you more right than another person just because he has a "lower" title than you.

Nothing beats beeing allowed to pick when i come in for work. Also today is pretty chill. Building is halv empty and i only have to write a lil documentation for kubernetes :D

I like the Kubernetes open source project. Big project that has been fairly good at smoothing things out and pushing the project forward.

3rd day at my new job.

Working for the first time in my life with CI & CD using Jenkins and Kubernetes, things I've wanted to integrate into my old job workflow since forever but couldn't due to business reasons.

Plus, first merge to production today after passing e2e tests.

I love where this is going.

(Getting used to Mac is the real PITA, though)

In a *redacted* company when I have started, there was a single wordpress site for an instance, no backups, no rescheduling, no nothing, so I have moved it to kubernetes and it is running for over a month smoothly without a sysadmin (me)

Yay!! Kubernetes finally running time to learn the basics !!

Everyone rides on k8s today....

But in the end it's just like Docker Swarm and Compose combined.

I don't know if Google is playing Elon Musk anymore.

Updated our rancher setup today and it just completely fucked the server, kubernetes stopped working, rancher stopped working. Guess who's going to install kubernetes manually next week? ;--;

How many sh*t days does it need to make me down?
3 ...

I hate my company, for making everything overcomplicated and annoying.... I have to discuss with 3 peoples for 3 days to getting some gitlab premium licenses (20$ per month for 10 licenses)... Why do you need it? Why we can't use the free version? Why Why Why... It's not enough to tell them it will save us much times and improves the quality of development.....

Also I wanted to ask if we can to Jaxb or another Dev Conference this year... Then I got the information that we have about 2000 Euro for 10 people for training.......... What should we do if everyone buys a book this budget is out .... f*ck company....

Second day, half of the day was taken for fixing the live db on the fly cause of a bad structure of tables... at least fixed some other inconsistence too... later the day fixed a freaking shitty bug with Spring Devtools and 2 Classloader to make the product that I'm presenting in 2 days running.

Today next shitty day with discussion that everything I did last half year (introducing Microservices, Kubernetes, Kafka and other DevOps things) could be maybe useless when the external company will say that they use another ecosystem -..- for their microservices...

Someone looking for a disappointed java developer? I just want to develop the best product ever... I'm happy with every area... Frontend, Backend, DevOps, Fullstack, Architect in some kinds depends on the wishes and technologies.

Just finished my Kubernetes book... This little piece of tech is amazing!!

This story is related to Docker containers.

Three years back when I heard about docker my first impression of docker was mini Virtual Machine. Then when you start your first container it’s no way to get out apart from pressing ctrl+d or leaving it like a screen. One of the most embarrassing thing with it was I tried really really hard to setup SSH on one of the container to log in there somehow. Then I understood how to use Dockerfiles and the command called `docker exec`

I thought Dockerfiles are the most amazing thing I have ever used for docker. But then I got introduced to docker-compose, and now it’s same with kubernetes

Now a days I read most of the document before doing hands-on on any new technology.

Learn:

Docker, kubernetes, ceph, s3, and aws in general. Not really dev per se, but still worthy technical goals.

Debugging your application on a mesosphere cluster for the first time.

Just got accepted to DigitalOcean's Kubernetes Limited Availability! Can't wait to test it out 😊

I am literally tasked with debugging why we have a 1.98 seconds lag on our site running on kubernetes. Smh

I hope it fucking work this time, kubernetes has been on my damn list since last summer, gave up on my 2Mbits internet so I took a scaleway server with 200mbits let's hope I get it to work this time!

I promised to blow off unit tests, so here we go. Let’s talk about unit tests.

Why use them? So, unit testing connoisseurs outline two big purposes:
1. To keep application integrity,
2. To catch bugs.

Keeping app integrity is when your freshly hired developer implement something that potentially leads to the whole app failure, but unit test fails and tell you that newly added code is breaking the app.

Catching bugs is pretty much self explanatory. Just think about it – you have to actually write code that describes how to check up another code to catch bugs in it.

I personally hate unit tests. I can’t explain, but every time I forced myself to write them, I got vertigo and terrible headache to the end of the day. Trying to write some tests? Here you go, wooosh and you can’t work anymore. Go get some sleep if you can.

But I still needed my job to be done and it should have been done really well. So I started my research.

Recalling Steve McConnell’s and many other classy developers’ experience, there is only one decent solution that prevents bugs and inconsistencies at large scale – the specs. Developing the specs should be considered the task number one. With decent, robust specs, app is almost guaranteed to contain no bugs.

Let’s take a look at the piece of great spec. For example, imagine you have to implement validation logic. So you state that validation should be implemented with special validation functions and then you define what validation function is: a pure function that accepts a value and returns boolean: true if value is good, false otherwise.

With that in mind, it’s obvious that potentially present bugs can only be inside that pure functions. Our spec made implementing validation very easy and idiomatic, isolating potential bugs. As soon as validators are pure and simple, unit tests aren’t needed at all.

You know what? As your app scales, you’ll definitely need a spec, sooner or later. Growing up without spec leads to irreversible failure, your app will grow like cancerous cell does and it’ll be easier to just put it into trash and start up from scratch.

But specs have one major downside – it requires at least one enlightened developer with really great experience to create it. It can’t be done quickly, it’s a very costly and difficult process. That’s why making great software costs that much.

But what if you need an MVP right now?

Speaking of MVPs, you’ll have to go with simplest instruments possible. Throw away Jenkins, use your Plesk autodeploy from Git repo. Throw away complex frontend setups, go with $30-$40 glittery ui kit or even an open source thing right from CDN, without less, sass, gulp and all that jazz. Make use of create-react-app if you can’t avoid using React because you’re making a web application.

Throw away AWS, Azure, Docker, Kubernetes and everything like that. Buy a cheap PHP7 hosting with pre-installed MySQL and do everything as simple as possible. If you have to use NoSQL, go with free Heroku with git autodeploy, NodeJS Express and free Mongo addon.

MVP should be ready in two weeks. As soon as your infrastructure is that simple, you don’t need unit tests. They’ll slow you down. Once you MVP is ready, go get funding, throw away first MVP, hire a decent CTO and let him create the spec.

Right there, it may be noticeable that unit tests are probably the biggest and baddest workaround imaginable. It gives you false sense of controlling your bugs, while you don’t have any control at all. Obvious bugs that unit tests can catch are easily noticeable at concise system, while quirky bugs couldn’t be caught by them because you can’t even imagine them while writing your unit tests. At this point, unit tests are just waste of time.

So, the whole picture is clear: at a small scale, you don’t have time to write unit tests and don’t have many bugs because of simple tools and standard patterns. At large scale, you need a spec to prevent bugs, unit tests become redundant as long as your spec is good.

In conclusion, I can tell that I’ve been developing a Clojurescript + CouchDB app for some startup, and in 8 month coding by spec I made myself I encountered only two or three bugs, all related to external JS tools and its quirks.

Have a good time!

credits to @arungupta kubernetes mom

Rails, React, React-Native, Docker, Kubernetes, Openstack, Jenkins, AWS, Microservices, Realm, MongoDB, PostgresQL, GraphQL (list goes on...), and I'm not even done yet.

6 months was spent learning all of the above because I found a Rails-only monolith on Heroku unsettling. My first batch of containers was just deployed and I couldn't be happier. Love my job.

Any devs out there worked building Golang microservices for a production environment?

I don’t have a specific question really. Just wondering who is out there on a similar path!

I’m building using Golang, Google Cloud, Docker, Kunernetes, and Terraform currently on a personal product bound for production!

Installed centos 7, docker, standalone kubernetes on dev machine in 20 minutes.
Spend 8 hours starting fucking dashboard service, still no fucking luck, no fucking logs, nothing.
Fucking pending states without fucking explanation.
All the fucking pods are running fine except one fucking dashboard. I want to see the fucking dashboard.
Fucking shit fuck.
Probably as always if I clean the machine and reinstall everything it would start normally, without fucking problem.
Debugging fucking containers is so much pain in the ass, fuck.
I think it’s enough for today.

Soo.. Not default?

So being in ops, I have certifications in networking and Linux, and am currently working on my Certified Kubernetes Administrator exam.

I've been talking to a few "professional" (they have jobs) devs that I personally know, and with the exception of 1, it seems like version control, automation, networking, and server related tasks are beyond them.

As I want to get into the dev side of things (devops preferably), I feel somewhat overwhelmed at some of the requirements of the job, especially knowing that I cannot take too much of a pay hit as I have a family to support.

My question is this, based on real world experiences with hiring, how much weight do you think knowing your way around networks, cloud, virtualization, servers, and all of the other things ops does when it comes to getting your foot in the door for a dev job?

I've casually looked around, and it seems that getting the foot in from this side is almost impossible.

Sharded Deployments on Kubernetes

When a CS student asks me (business IT student) how he can get kubernetes to work in PHP.
(No, I did not swap those two)
*facepalm*

I fucking hate the Nginx Ingress Controller for Kubernetes. Fucking piece of shit. You fucking can't do a fucking simple rewrite and proxy pass???? Fucccck!

Hello, there is some good tutorial about kubernetes?

Thanks

Does anyone of you guys use Kubernetes? If yes, what setup do you have?

It took me 48 hours ( not continuously) to fix a bug by going through a cluster fuck code of multiple modules. Tracing the error through 5 or 6 layers. And u dont get error logs right away. You need to recreate that error and see the logs on a kubernetes pod. Just to find out the bug was a duplicate.
Yes jokes are on me. I fucked up by not checking for duplicate. I steered right away on that shit dipped bug like a hungry/zombie hound. Fuck me.

That moment when you are so impressed about someone or something and interested and want to talk about it but you dont know how to even string two sentances about it even after you just spoke to someone that got you interested in it.

Time to spend a few hours getting the lingo down but in short, using python to make a FE to allow users to create a Hermes config file that will be used on Kubernetes to set up clusters of servers on aws to run their version of our platform. My mind is so rekt and i thank the Devops guys for this needed break from the FE where i normally reside. I love working with people that are not only good but enjoy what they do. They make me a better developer myself 👏

This is one of the many vast reasons i love what i do and having a place to share with more like-minded induviduals like yourself, im grateful.

Thabks for reading and hope you have or had a great day. Keep up the good work all and stay focused 👌

"This service runs outside of k8s so it can only be accessed from other services in prod"

Yay... Don't you love it when things can't be run outside of prod...

Learn Scala, Akka, C#, Kubernetes, and improve my Python.

spends almost 5 weeks trying to get CI/CD to work with Kubernetes (including installing Kubernetes itself).
Decides that he might go see if Nomad is a better thing for him...
Man, if only I discover stuff sooner...

Collegue texted me that the sites arent working, so I have tested them and they do work, but when the proxy is up, so I went to investigate what is the problem. It turns out that traefik automagically gets a termination from somewhere and kubernetes views that as a error on exit, so restarts it, but why does it exit? I have debug logging enabled and no error there. Wtf?!?! Think it will be a long night or morning 😀🙂😐😑😣😫

I just setup Jenkins locally for the first time to do some CI/CD for a project using docker. Then I upgraded the container to the latest version of Jenkins.

I am liking it so far but haven’t really setup anything significant yet.

Any of you ranters have experience with Jenkins?

- would you recommend it. Pros/cons?

- what resources did you use to setup and expand your pipelines?

- any experience with Google Cloud Platform and Jenkins.

These are kind of open ended questions to start a discussion on the topic.

Jenkins will be used at least for deploying the front end built in React. I may also use it for deployment if the Golang API but that uses Kubernetes at the moment.

So I have a major deployment to do tomorrow. 8 repos. So 8 seperate deploys. Wish me luck.

Best book/source for learning everything devops'y'/kubernetes?

(Given that I have some sort of experience in Dockers, hosting websites and know a fracture of aws archeticture, but lack in good "cloud" thinking skills, scalability, understanding costs for production applications, cluster size, etc...)

Why is it so hard to setup and learn Kubernetes? :c

Started openshift to make send some of apps to cloud, damn it is too annoying. Everything is like 4x time consuming and hard, documentation really lacks, you google some errors? well answer is in red hat site and you can only see that if you are paid subscriber, issues in github are closed randomly(generally like we are going to fix this so no open issues??-written in 2017). If i had any other chance i would take it, like instantly.

I guess these days I work with Golang, gRPC, and Kubernetes. I guess that's a dev stack. Or turning into one at the very least. The only thing that annoys me about this stack, is how different deployments for kubernetes are different for CSPs. The fact that setting up a kubernetes/Golang dev environment is take a lot of time and effort. And gRPC can be a pain in the ass to work with as well. Since it's fairly new in large scale enterprise use, finding best practices can be pretty hard, and everything is "feet in the fire" and "trial by error" when dealing with gRPC.

And Golang channels can get very hairy and complicated really really fast. As well as the context package in Golang. And Golang drama with package managers. I wish they would just settle on GoDeps or vgo and call it a day.

And for the love of God, ADD FUCKING GENERICS! Go code can be needlessly long and wordy. The alternative "struct function members" can be pretty clunky at times.

Questions around Openshift:

My company is actually triying to find out if Openshift is a thing out in the developers world. We are currently (finally) investing some money in container architectures. But are quite unsure if Openshift is a real thing out there. So my questions:

For how long are you building Openshift application PODs and why?

Or alternatively: Do you know a good source of up to date surveys around the container world, or do you know who can do good and usable surveys in that kind of area?

Still working on setting up my Kubernetes cluster. Jesus Fuck this is complicated

*tries to build a Kubernetes cluster*
*gets error while trying to install Flannel*

crap...

Cloudfoundry Docker Diego Kubernetes. Loved working on the set. What about alternatives?

Hello guys,

is it good for every use-case to have a own ecs / kubernetes cluster?
It thinks yes, whats your opinion?

Greets Jonathan