The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Network Policy is a critical part of building a robust developer platform, but the learning curve to address complex real-world policies is not tiny. It is painful to get the YAML syntax right. There are many subtleties in the behavior of the network policy specification (e.g., default allow/deny, wildcarding, rules combination, etc.). Even an experienced Kubernetes YAML-wrangler can still easily tie their brain in knots working through an advanced network policy use case.
In this post we’ll explore the concepts of data lake, data hub and data lab. There are many opinions and interpretations of these concepts, and they are broadly comparable. In fact, many might say they’re synonymous and we’re just splitting hairs. But let’s look again carefully. We can discern some subtle trends in the way people are doing things, and find distinctions in these expressions.
Your users access your application from a wide range of browsers, which have their own implementations of HTML, CSS, and JavaScript. For instance, many modern JavaScript features such as Promises and Arrow Functions are unsupported by some browsers. These inconsistencies can lead to missing elements and malfunctioning workflows that affect some—but not all—of your user base.
If you’ve already connected your GitHub integration via OAuth in GitKraken, you’re good to go! GitHub is changing its security policy and will no longer allow username/password-only access. This change goes into effect on August 13th, 2021, and affects all desktop Git applications that offer a GitHub integration, including GitKraken. Users who have already authenticated to GitHub using OAuth will be unaffected. OAuth is the default connection method within your GitKraken profile settings.