<commit_before># CVE-2017-14491

A vulnerability in dnsmasq, used by kube-dns, requires an upgrade to the
kube-dns component. This component is the default DNS component installed in
Kubernetes.  The vulnerability may be externally exploitable. Links below exist
with the full detail of the CVE. This exploit is not a Kubernetes specific vulnerability but exists in dnsmasq.

## Current kops Status

`kops` release 1.7.1 addresses this CVE.  This version of `kops` will upgrade and
create clusters. `kops` 1.8.0.alpha.1 release does not contain the required
changes, but when released 1.8.0.apha.2 will contain the required patches.

## Upgrading Cluster

The kube-dns deployment will be automatically upgraded when `kops update
cluster` is executed. Replace `my-cluster.example.com` with the name of your
cluster.  If you are upgrading a Kubernetes 1.4.x or 1.5.x cluster you may need
to follow  the instruction below to create a required confimap for kube-dns.

Upgrade command:

```bash
kops update cluster --yes --name my-cluster.example.com
```

Validate the change was applied to the deployment:

```bash
kubectl get deployment -n kube-system kube-dns \
-o jsonpath='{.spec.template.spec.containers[?(@.name == "dnsmasq")].image}'
```

The upgrade is will occur once the channels utilty picks up the change within a
few minutes.<commit_msg>Typo delete duplicated "is ", "utilty"->"utility"<commit_after># CVE-2017-14491

A vulnerability in dnsmasq, used by kube-dns, requires an upgrade to the
kube-dns component. This component is the default DNS component installed in
Kubernetes.  The vulnerability may be externally exploitable. Links below exist
with the full detail of the CVE. This exploit is not a Kubernetes specific vulnerability but exists in dnsmasq.

## Current kops Status

`kops` release 1.7.1 addresses this CVE.  This version of `kops` will upgrade and
create clusters. `kops` 1.8.0.alpha.1 release does not contain the required
changes, but when released 1.8.0.apha.2 will contain the required patches.

## Upgrading Cluster

The kube-dns deployment will be automatically upgraded when `kops update
cluster` is executed. Replace `my-cluster.example.com` with the name of your
cluster.  If you are upgrading a Kubernetes 1.4.x or 1.5.x cluster you may need
to follow  the instruction below to create a required confimap for kube-dns.

Upgrade command:

```bash
kops update cluster --yes --name my-cluster.example.com
```

Validate the change was applied to the deployment:

```bash
kubectl get deployment -n kube-system kube-dns \
-o jsonpath='{.spec.template.spec.containers[?(@.name == "dnsmasq")].image}'
```

The upgrade will occur once the channels utility picks up the change within a
few minutes.
{'fraction_non_alphanumeric': 0.07887013939838591, 'fraction_numerical': 0.01760821716801174, 'mean_word_length': 4.30544747081712, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 4, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '225941', 'n_tokens_mistral': 856, 'n_tokens_neox': 786, 'n_words': 366}