-- Leo's gemini proxy
-- Connecting to gemini.tuxmachines.org:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini;lang=en-GB
Tux Machines
Posted by Roy Schestowitz on May 12, 2023
> Week 18 (May 4th - May 9th) # We have experienced issues with automatic Bodhi updates that we are investigating. In case you miss a Bodhi update, you can retrigger the job via /packit create-update comment in a dist-git pull request. Besides that, during this short week (another Czech Republic public holiday) we didn’t manage to implement any significant new features.
> Open-source computing is facing an inflection point when it comes to enterprise use cases. The recent surge in artificial intelligence presents a challenge to open source and could potentially topple generations of open-source work. “No one wants to bet against open source,” said industry analyst John Furrier (pictured, left).
> Flapi, the Flatpak Installer, was in need of this: the user is now able to add entries.
> Before getting onto that though, a report on more apps added to Flapi. Here is the previous report:
> https://bkhome.org/news/202305/more-flatpaks-added-to-the-installer.html
> Have added some more: [...]
> In Kubernetes, a Service can be used to provide a unified traffic endpoint for applications running on a set of Pods. Clients can use the virtual IP address (or VIP) provided by the Service for access, and Kubernetes provides load balancing for traffic accessing different back-end Pods, but a ClusterIP type of Service is limited to providing access to nodes within the cluster, while traffic from outside the cluster cannot be routed. One way to solve this problem is to use a type: NodePort Service, which sets up a mapping to a specific port of all nodes in the cluster, thus redirecting traffic from the outside to the inside of the cluster.
> When a type: NodePort Service is created, its corresponding port(s) are allocated in one of two ways:
> Dynamic : If the Service type is NodePort and you do not set a nodePort value explicitly in the spec for that Service, the Kubernetes control plane will automatically allocate an unused port to it at creation time.
> Static : In addition to the dynamic auto-assignment described above, you can also explicitly assign a port that is within the nodeport port range configuration.
> The value of nodePort that you manually assign must be unique across the whole cluster. Attempting to create a Service of type: NodePort where you explicitly specify a node port that was already allocated results in an error.
> Forums are excellent online discussion platforms where users can share their insights, concepts, and viewpoints on a variety of topics. They are commonly used for community building, customer support, and knowledge sharing.
-- Response ended
-- Page fetched on Sat Jun 1 09:16:52 2024