cpressland
Now
•
100%
I really enjoyed this one, as a modern Mac user who bought into the classic ecosystem a few years ago and ended up writing a Raspberry Pi Modem + BeautifulSoup adapter for the modern web this was quite amusing for me. Was surprised not to see a Dock considering they said it was running System 7.5, which I'm fairly sure had a "Dock" like extension out of the box.
cpressland
Now
•
100%
At work we’re a Azure house. When Microsoft announced Bicep I genuinely laughed and was like “why would I ever want this?!”.
I get it now.
cpressland
Now
•
100%
This is a godsend!! Thank you so much!
cpressland
Now
•
90%
Question to the community: would you like these YouTube videos posted here for discussion?
cpressland
Now
•
100%
Doing what’s right is always wrong if it’s against a large corporation. I’m grateful to HashiCorp for making Terraform, but I’m absolutely done with them as a company.
cpressland
Now
•
92%
can be waved away by disclosure and a promise not to let it color your conclusions.
I don’t think it’s ever been stated that the framework investment hasn’t lead to direct criticism of competing products. The disclosure is there to let us know that there is pre-existing bias in the upcoming review.
This is similar to watching Mac Address and being pissed off that they have a bias towards Macs.
cpressland
Now
•
93%
In my terrible attempt and translating to German… “einer von uns, einer von uns, einer von uns”!
cpressland
Now
•
100%
The list had no intended ordering, but I will admit my community was listed first entirely for selfish reasons.
I could have a bot update the list automatically with new communities and order them by subscriber size if you think that’d be fairer?
cpressland
Now
•
80%
I do 0900-1800, lunch isn’t included for me. But I’m also fortunate enough to work for a company that only does four days a week.
cpressland
Now
•
100%
My apologies, I’ll setup an account on kbin and figure out the correct formatting a bit later today.
cpressland
Now
•
87%
Outstanding!! Bookmarked, thank you!
cpressland
Now
•
100%
With federation, you can have as many rimjob_steve’s as you like! 😁
cpressland
Now
•
100%
My pleasure! Thanks!
cpressland
Now
•
94%
True, but discoverability on Reddit was much much easier, I’ve found this to be one of Lemmys weakest attributes so far. I’m sure it’ll improve over time or somebody will make a search engine based on the instance map over on GitHub.
Hmm, that’s not a bad idea. I might give that a try at some point.
cpressland
Now
•
66%
This’d usually be something a bot would do. I use one over on !ltt@devops.pizza to keep an eye on things but I don’t let it post/comment as I want to encourage the community to actively post and not just lurk.
But if posting news to all LTT communities is something the respective community members and moderators are happy to see, I could add that as a feature.
One of the key differences between traditional social media and the Fediverse is the existence of multiple communities that share the same topic. You should have a choice when it comes to your community preferences so I wanted to create a list of other LTT/LMG communities on the Fediverse to help us all grow. If you’re aware of a community I’ve missed, please comment them below and I’ll update the post body. - [!ltt@devops.pizza](https://devops.pizza/c/ltt) - [!linustechtips@lemmy.ml](https://lemmy.ml/c/linustechtips) - [!linustechtips@lemmit.online](https://lemmit.online/c/linustechtips) - [!linustechtips@lemmy.world](https://lemmy.world/c/linustechtips) - [!LinusTechTips@kbin.social](https://kbin.social/m/LinusTechTips) - [!linus_tech_tips@discuss.online](https://discuss.online/c/linus_tech_tips)
One of the key differences between traditional social media and the Fediverse is the existence of multiple communities that share the same topic. You should have a choice when it comes to your community preferences so I wanted to create a list of other LTT/LMG communities on the Fediverse to help us all grow. If you’re aware of a community I’ve missed, please comment them below and I’ll update the post body. - [!ltt@devops.pizza](https://devops.pizza/c/ltt) - [!linustechtips@lemmy.ml](https://lemmy.ml/c/linustechtips) - [!linustechtips@lemmit.online](https://lemmit.online/c/linustechtips) - [!linustechtips@lemmy.world](https://lemmy.world/c/linustechtips) - [!LinusTechTips@kbin.social](https://kbin.social/m/LinusTechTips) - [!linus_tech_tips@discuss.online](https://discuss.online/c/linus_tech_tips)
One of the key differences between traditional social media and the Fediverse is the existence of multiple communities that share the same topic. You should have a choice when it comes to your community preferences so I wanted to create a list of other LTT/LMG communities on the Fediverse to help us all grow. If you’re aware of a community I’ve missed, please comment them below and I’ll update the post body. - [!ltt@devops.pizza](https://devops.pizza/c/ltt) - [!linustechtips@lemmy.ml](https://lemmy.ml/c/linustechtips) - [!linustechtips@lemmit.online](https://lemmit.online/c/linustechtips) - [!linustechtips@lemmy.world](https://lemmy.world/c/linustechtips) - [!LinusTechTips@kbin.social](https://kbin.social/m/LinusTechTips) - [!linus_tech_tips@discuss.online](https://discuss.online/c/linus_tech_tips)
One of the key differences between traditional social media and the Fediverse is the existence of multiple communities that share the same topic. You should have a choice when it comes to your community preferences so I wanted to create a list of other LTT/LMG communities on the Fediverse to help us all grow. If you’re aware of a community I’ve missed, please comment them below and I’ll update the post body. - [!ltt@devops.pizza](https://devops.pizza/c/ltt) - [!linustechtips@lemmy.ml](https://lemmy.ml/c/linustechtips) - [!linustechtips@lemmit.online](https://lemmit.online/c/linustechtips) - [!linustechtips@lemmy.world](https://lemmy.world/c/linustechtips) - [!LinusTechTips@kbin.social](https://kbin.social/m/LinusTechTips) - [!linus_tech_tips@discuss.online](https://discuss.online/c/linus_tech_tips)
One of the key differences between traditional social media and the Fediverse is the existence of multiple communities that share the same topic. You should have a choice when it comes to your community preferences so I wanted to create a list of other LTT/LMG communities on the Fediverse to help us all grow. If you’re aware of a community I’ve missed, please comment them below and I’ll update the post body. - [!ltt@devops.pizza](https://devops.pizza/c/ltt) - [!linustechtips@lemmy.ml](https://lemmy.ml/c/linustechtips) - [!linustechtips@lemmit.online](https://lemmit.online/c/linustechtips) - [!linustechtips@lemmy.world](https://lemmy.world/c/linustechtips) - [!LinusTechTips@kbin.social](https://kbin.social/m/LinusTechTips) - [!linus_tech_tips@discuss.online](https://discuss.online/c/linus_tech_tips)
cpressland
Now
•
100%
Okay, “media engine”. My mistake.
cpressland
Now
•
90%
Consider crossposting this to !linustechtips@lemmy.ml for wider community engagement as that community currently has more subscribers than here. Hopefully the mod over there is reasonable this time and agrees this is fantastic progress in the right direction.
cpressland
Now
•
100%
Can you give some more context around what this is? Happy to try and replicate if you can provide some steps.
cpressland
Now
•
100%
Fedora is a tough one for me, on one hand I like the design principles of the OS, Systemd heavy unlike Debian / Ubuntu that still uses some old school init scripts etc. On the other hand, the association with Red Hat makes me want to steer well clear of it.
Asahi Fedora Linux is likely the thing that’ll force me down this fedora shaped rabbit hole.
github.com
This release introduces direct pod-to-pod multicluster service mirroring. When clusters are deployed on a flat network, Linkerd can export multicluster services in a way where cross-cluster traffic does not need to go through the gateway. This enhances multicluster authentication and can reduce the need for provisioning public load balancers. In addition, this release adds support for the Gateway API HTTPRoute resource (in the gateway.networking.k8s.io api group). This improves compatibility with other tools that use these resources such as Flagger and Argo Rollouts. The release also includes a large number of features and improvements to HTTPRoute including the ability to set timeouts and the ability to define consumer-namespace HTTPRoutes. Finally, this release includes a number of bugfixes, performance improvements, and other smaller additions. Upgrade notes: Please see the [upgrade instructions](https://linkerd.io/2/tasks/upgrade/#upgrade-notice-stable-2140). * Multicluster * Remove namespace field from cluster scoped resources to fix pruning * Added -o json flag for the linkerd multicluster gateways command (thanks @hiteshwani29) * Introduced logFormat value to the multicluster Link Helm Chart (thanks @bunnybilou!) * Added leader-election capabilities to the service-mirror controller * Added high-availability (HA) mode for the multicluster service-mirror * Added a new remoteDiscoverySelector field to the multicluster Link CRD, which enables a service mirroring mode where the control plane performs discovery for the mirrored service from the remote cluster, rather than creating Endpoints for the mirrored service in the source cluster * HTTPRoute * Fixed linkerd uninstall issue for HTTPRoute Added support for gateway.networking.k8s.io HTTPRoutes in the policy controller * Added support for RequestHeaderModifier and RequestRedirect HTTP filters in outbound policy; filters may be added at the route or backend level * Added support for the ResponseHeaderModifier HTTPRoute filter * Added support for HTTPRoutes defined in the consumer namespace * Added support for HTTPRoute parent_refs that do not specify a port * CRDs * Patched the MeshTLSAuthentication CRD to force providing at least one identity/identityRef * Control Plane * Send Opaque protocol hint for opaque ports in destination controller * Replaced deprecated failure-domain.beta.kubernetes.io/zone labels in Helm charts with topology.kubernetes.io/zone labels (thanks @piyushsingariya!) * Replaced server_port_subscribers Destination controller gauge metric with server_port_subscribes and server_port_unsubscribes counter metrics * Proxy * Handle Opaque protocol hints on endpoints * Added outbound_http_balancer_endpoints metric * Fixed missing route_ metrics for requests with * ServiceProfiles * Fixed proxy startup failure when using the config.linkerd.io/admin-port annotation (thanks @jclegras!) * Added distinguishable version information to proxy logs and metrics * CLI * The linkerd diagnostics policy command now displays outbound policy when the target resource is a Service * A fix for HA validation checks when Linkerd is installed with Helm. Thanks @mikutas!! * Viz * Add the kubelet NetworkAuthentication back since it is used by the linkerd viz allow-scrapes subcommand. * Fixed the linkerd viz check command so that it will wait until the viz extension becomes ready * Fixed an issue where specifying a remote_write config would cause the Prometheus config to be invalid (thanks @hiteshwani29) * Improved validation of the --to and --from flags for the linkerd viz stat command (thanks @pranoyk) * Added -o jsonpath flag to linkerd viz tap to allow filtering output fields (thanks @hiteshwani29!) * Fixed a Grafana error caused by an incorrect datasource (thanks @albundy83!) * Fixed missing "Services" menu item in the Spanish localization for the linkerd-viz web dashboard (thanks @mclavel!) * Extensions * Added missing label linkerd.io/extension to certain resources to ensure they pruned when appropriate (thanks @ClementRepo) * Added tolerations and nodeSelector support in extensions namespace-metadata Jobs (thanks @pssalman!) * Init Containers * Added an option for disabling the network validator's security context for environments that provide their own * CNI * Added --set flag to install-cni plugin (thanks @amit-62!) * Fixed missing resource-cni labels on linkerd-cni, this blocked the linkerd-cni pods from coming up when the injector was broken (thanks @migueleliasweb!) * Build * Build improvements for multi-arch build artifacts. Thanks @MarkSRobinson!!
Now