Update blog post to include the fix version and fix the link to the PR

Signed-off-by: Charles Pretzer <charles@charlespretzer.com>
This commit is contained in:
Charles Pretzer
2021-10-05 14:33:40 -07:00
parent e433c954d0
commit e5aca814aa
@@ -144,10 +144,9 @@ ways to address it.
- Specifically add an iptables rule to drop the packets that are marked as - Specifically add an iptables rule to drop the packets that are marked as
*INVALID*, so it wont reach to client pod and cause harm. *INVALID*, so it wont reach to client pod and cause harm.
The fix is drafted (https://github.com/kubernetes/kubernetes/pull/74840), but The [fix](https://github.com/kubernetes/kubernetes/pull/74840) is available in v1.15+.
unfortunately it didnt catch the v1.14 release window. However, for the users However, for the users that are affected by this bug, there is a way to mitigate the
that are affected by this bug, there is a way to mitigate the problem by applying problem by applying the following rule in your cluster.
the following rule in your cluster.
```yaml ```yaml
apiVersion: extensions/v1beta1 apiVersion: extensions/v1beta1