4 ms·

> once you set up a decently tricked out Helm chart I don't disagree but this condition is doing a hell of a lot of work. To be fair, you don't need to do muc

by ljm 5y ago

> once you set up a decently tricked out Helm chart I don't disagree but this condition is doing a hell of a lot of work. To be fair, you don't need to do much to run a service on a toy k8s project. It just gets complicated when you layer on all production grade stuff like load balancers, service meshes, access control, CI pipelines, o11y, etc. etc.

edoceo 5y ago
o11y = observability
- tovej 5y ago
  You couldn't create a parody of this naming convention that's more outlandish than the way it's actually being used.
  - handrous 5y ago
    o11y? In my head it sounds like it's a move in "Tony Hawk: Pro K8er"
  - hnick 5y ago
    You don't like n7ms?
  - grp000 5y ago
    It's the Wingdings of naming conventions.
  - tsechin 5y ago
    Yes you can! Accessibility gets abbreviated to a11y, which is about as inaccessible as it gets.
    - hnbad 5y ago
      Only if you've never seen it before. The word "accessibility" is incredibly inaccessible to non-native speakers and native speakers with learning disabilities or dyslexia. There's some double characters in there but which ones? Also it sounds like there's an a or "uh" sound in there but somehow it's all "i"s except one is an "e"? "a11y" is four letters (well, two of them are digits but who's counting?) and clearly refers to one particular concept. Likewise "i18n" (internationalization/internationalisation) and "l10n" (localization/localisation) avoids confusion of whether it's "ize" or "ise", which is literally the problem those concepts try to solve. I can somewhat excuse "k8s" with "nobody can remember how kubernetes is spelled let alone pronounced" (Germans insist pronouncing the "kuber" part the same way "kyber/cyber" is pronounced in other Greek loanwords, with a German "ü" umlaut) but I admit that one is a stretch and "visual puns" like "k0s" ("minimal", you see?) and "k3s" (the digit 3 looks like half of an 8 so it's "lightweight", right?) are a bit beyond the pale for me.
      - oalae5niMiel7qu 5y ago
        >The word "accessibility" is incredibly inaccessible to non-native speakers There are at least a dozen languages where the English word "accessibility" translates to the same word spelled slightly differently.
        hnbad 5y ago
        I'm not sure what your point is. I qualified my claim very explicitly and what you said doesn't contradict any of it. I'm not saying it's difficult to understand. I'm saying it's an unwieldy word and "a11y" is easier to remember and write correctly.
        oalae5niMiel7qu 5y ago
        You specifically called it out as being "inaccessible" (ie, difficult to understand) to non-native speakers (of English). Also, "a11y" looks too much like the English word "ally". That, IMO, is more likely to cause reading difficulties, particularly with non-native speakers and people with dyslexia.
- oogali 5y ago
  I was originally confused because I thought the debugger `ollydbg` was being referenced. https://en.wikipedia.org/wiki/OllyDbg https://en.wikipedia.org/wiki/OllyDbg
verdverm 5y ago
You still have to do that prod grade stuff, K8s creates a cloud agnostic API for it. People can use the same terms and understand each other
nickjj 5y ago
> To be fair, you don't need to do much to run a service on a toy k8s project. The previous reply is based on a multi-service production grade work load. Setting up a load balancer wasn't bad. Most cloud providers that offer managed Kubernetes make it pretty painless to get their load balancer set up and working with Kubernetes. On EKS with AWS that meant using the AWS Load Balancer Controller and adding a few annotations. That includes HTTP to HTTPS redirects, www to apex domain redirects, etc.. On AWS it took a few hours to get it all working complete with ACM (SSL certificate manager) integration. The cool thing is when I spin up a local cluster on my dev box, I can use the nginx ingress instead and everything works the same with no code changes. Just a few Helm YAML config values. Maybe I dodged a bullet by starting with Kubernetes so late. I imagine 2-3 years ago would have been a completely different world. That's also why I haven't bothered to look into using Kubernetes until recently. > I don't disagree but this condition is doing a hell of a lot of work. It was kind of a lot of work to get here, but it wasn't anything too crazy. It took ~160 hours to go from never using Kubernetes to getting most of the way there. This also includes writing a lot of ancillary documentation and wiki style posts to get some of the research and ideas out of my head and onto paper so others can reference it.

by ljm 5y ago

edoceo 5y ago

o11y = observability

tovej 5y ago
You couldn't create a parody of this naming convention that's more outlandish than the way it's actually being used.
- handrous 5y ago
  o11y? In my head it sounds like it's a move in "Tony Hawk: Pro K8er"
- hnick 5y ago
  You don't like n7ms?
- grp000 5y ago
  It's the Wingdings of naming conventions.
- tsechin 5y ago
  Yes you can! Accessibility gets abbreviated to a11y, which is about as inaccessible as it gets.
  - hnbad 5y ago
    Only if you've never seen it before. The word "accessibility" is incredibly inaccessible to non-native speakers and native speakers with learning disabilities or dyslexia. There's some double characters in there but which ones? Also it sounds like there's an a or "uh" sound in there but somehow it's all "i"s except one is an "e"? "a11y" is four letters (well, two of them are digits but who's counting?) and clearly refers to one particular concept. Likewise "i18n" (internationalization/internationalisation) and "l10n" (localization/localisation) avoids confusion of whether it's "ize" or "ise", which is literally the problem those concepts try to solve. I can somewhat excuse "k8s" with "nobody can remember how kubernetes is spelled let alone pronounced" (Germans insist pronouncing the "kuber" part the same way "kyber/cyber" is pronounced in other Greek loanwords, with a German "ü" umlaut) but I admit that one is a stretch and "visual puns" like "k0s" ("minimal", you see?) and "k3s" (the digit 3 looks like half of an 8 so it's "lightweight", right?) are a bit beyond the pale for me.
    - oalae5niMiel7qu 5y ago
      >The word "accessibility" is incredibly inaccessible to non-native speakers There are at least a dozen languages where the English word "accessibility" translates to the same word spelled slightly differently.
      - hnbad 5y ago
        I'm not sure what your point is. I qualified my claim very explicitly and what you said doesn't contradict any of it. I'm not saying it's difficult to understand. I'm saying it's an unwieldy word and "a11y" is easier to remember and write correctly.
        oalae5niMiel7qu 5y ago
        You specifically called it out as being "inaccessible" (ie, difficult to understand) to non-native speakers (of English). Also, "a11y" looks too much like the English word "ally". That, IMO, is more likely to cause reading difficulties, particularly with non-native speakers and people with dyslexia.
oogali 5y ago
I was originally confused because I thought the debugger `ollydbg` was being referenced. https://en.wikipedia.org/wiki/OllyDbg https://en.wikipedia.org/wiki/OllyDbg

verdverm 5y ago

You still have to do that prod grade stuff, K8s creates a cloud agnostic API for it. People can use the same terms and understand each other

nickjj 5y ago

> To be fair, you don't need to do much to run a service on a toy k8s project. The previous reply is based on a multi-service production grade work load. Setting up a load balancer wasn't bad. Most cloud providers that offer managed Kubernetes make it pretty painless to get their load balancer set up and working with Kubernetes. On EKS with AWS that meant using the AWS Load Balancer Controller and adding a few annotations. That includes HTTP to HTTPS redirects, www to apex domain redirects, etc.. On AWS it took a few hours to get it all working complete with ACM (SSL certificate manager) integration. The cool thing is when I spin up a local cluster on my dev box, I can use the nginx ingress instead and everything works the same with no code changes. Just a few Helm YAML config values. Maybe I dodged a bullet by starting with Kubernetes so late. I imagine 2-3 years ago would have been a completely different world. That's also why I haven't bothered to look into using Kubernetes until recently. > I don't disagree but this condition is doing a hell of a lot of work. It was kind of a lot of work to get here, but it wasn't anything too crazy. It took ~160 hours to go from never using Kubernetes to getting most of the way there. This also includes writing a lot of ancillary documentation and wiki style posts to get some of the research and ideas out of my head and onto paper so others can reference it.